[FEATURE] Resource btp_subaccount_subscription to support Custom or partner-developed applications about terraform-provider-btp HOT 7 CLOSED

The application you mentioned is a custom application, used by an SAP Partner.
Did not test that for quite sometime but yes, subscription via terraform should be working, it worked before.
I am not sure if that is officially supported though.

Can you compare your "btp_subaccount_subscription" resource with the one I have here?

from terraform-provider-btp.

@stefania-santimbrean if you have no plan name for your application, this might cause issues. You can hand over an empty string, but I am not sure if this does the trick. Can you register your app with an explicit plan name (e.g., default) and try the subscription to the app again?

from terraform-provider-btp.

Hello @lechnerc77 , @alperdedeoglu ,

Thanks for your suggestions! Indeed, I modified saas registry config in mta to have appPlan name default similar to this: https://github.com/SAP-samples/btp-cap-multitenant-saas/blob/main/deploy/cf/mta.yaml#L371 and it's now working!

Many thanks,
Stefania

from terraform-provider-btp.

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.

from terraform-provider-btp.

Hello @alperdedeoglu ,

What do you mean to compare "btp_subaccount_subscription" source?

Thanks,
Stefania

from terraform-provider-btp.

Subscription is created via a resource type called "btp_subaccount_subscription" in this file.

Please make sure that your SaaS Registry app name and plan name is precise and correct. It might be the reason that your app name or plan name are not matching therefore terraform provider can not find your application in the BTP Marketplace.

resource "btp_subaccount_subscription" "project" {
  subaccount_id = btp_subaccount.project.id
  app_name      = local.kyma ? "${var.app_name}-${var.namespace}-${var.shootname}" : "${var.app_name}-${var.space}-${var.org}"
  plan_name     = var.app_plan
}

from terraform-provider-btp.

Hello @alperdedeoglu ,

App name is for sure correct and plan name is "default" or to be more precise we do not specify a plan name when we configure the saas-registry service instance. But resource "btp_subaccount_subscription" has the field plan_name mandatory...

I am talking about a custom saas app. Subscription to HANA Tools for example works.

Thanks,
Stefania

from terraform-provider-btp.