[FEATURE] Support Integration Suite Capabilities

[lechnerc77]

What area do you want to see improved?

terraform provider

Is your feature request related to a problem? Please describe.

The Terraform Provider in its current state supports the creation of the integration suite per se i.e. the subscription to the application.
It is currently not possible to manage Integration Suite assets like Open Connector Flows via Terraform.

Describe the solution you would like

The management of integration suite assets namely the configuration should also be possible via Terraform. Here some pseudo code how this could look like

resource "btp_subaccount_subscription" "integration-suite" {
  subaccount_id = "you_subscr_id"
  app_name      = "it-cpitrial05-prov"
  plan_name     = "trial"
}

resource "btp_subaccount_integration_suite_open_connector" "s3_connector" {
  subaccount_id = "you_subscr_id"
  connector_tyoe = "s3"
  connector_type_id = "16"
  configuration = {
    access_key_id     = "your_access_key_id"
    secret_access_key = "your_secret_access_key"
    bucket_name       = "your_bucket_name"
    region_endpoint   = "your_region_endpoint"
  }
  name = "s3_connector"
}

Describe alternatives you have considered

Manual configuration but this breaks the automation flow and distributes the management of the resources.

Additional context

To be defined: while the management of capabilities of the Integration Suite should be covered by Terraform, the Deployment of Flows probably makes more sense to keep with the key users and , hence, keep it separated.

[lechnerc77]

Thanks for the feature request. We evaluate it and update the issue accordingly.

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[MartinPankraz]

Ideally the resources cover the individual CPI package and iflow including the adapter deployment:

I believe the iflow will need to be supplied as zip package, since it contains multiple files. An iFlow export would be the ideal kick off point.

[lechnerc77]

Ideally the resources cover the individual CPI package and iflow including the adapter deployment:

I believe the iflow will need to be supplied as zip package, since it contains multiple files. An iFlow export would be the ideal kick off point.

@MartinPankraz Would you make the iFlow deployment part of the Terraform flow for provisioning the artifacts and configurations or would you split that as a different persona is in charge of the iFlow design?

[MartinPankraz]

We need more evidence there what the customer's preferred option would be. Solution-wise, it is not functional without the iFlow provisioned to the tenant and deployed to the runtime. However, that was my north-start: a fully packaged solution that is operational after the tf deployment.

[lechnerc77]

Remark for maintainer team: Needs to be discussed after GA of Provider as this is a larger story and it needs to be decided how to best approach this (dedicated provider etc.)

[MartinPankraz]

Please consider SAP Edge Integration Cell as part of the story. A multitude of manual config steps are a challenge for scaling the deployment. Terraform would be a nice option to solve.

[Srinu3366]

It would be nice if we can use a data source to get the iFlow package from a tenant and deploy it using an integration_flow resource. Same can be applied for other types of artifacts.

[lechnerc77]

Status Update: This request is currently of lower priority in favor of #749 and #734 which are both currently under development