SAP CAP Object Store Deploy Cross Sub Account Pay as you go & CPEA issue

[TinhLeo]

Hi Expert,

I've an issue with the Object Store service plan difference between account Pas as you go and CPEA

The Reason:

Dev system sub-account Pas as you go: Object Store service plan is standard

UAT/PRD system sub-account CPEA: The object Store service plan is s3-standard

Workaround: I have manually edited the mta.yaml (service plan) to enter the CPEA Object Store service plan for UAT/PRD and then built it and deployed it to UAT/PRD subaccount. After this step, we need to revert the changes back for the Dev subaccount PAYG deployment, it's a little bit confusing and hard to manage the source code.

I might use Jenkins pipeline to inject properties of mta.yaml to set service plan for each sub-account but not pretty sure it's a good way

Question:  What is the right way to set the "service plan"  or other mapping parameter etc., so that the deployment works for both PAYG Subaccount and Production subaccount (CPEA), without manually changing it?

Please give me advice or best practice to deal with it

Thank you so much

[Dinu · Accepted solution]

Use MTA Extension Descriptors. You can define extension descriptor for every environment with the specifics of the environment. Checkout Configure same MTA for different environments [SAP-Samples].

[TinhLeo · Accepted solution]

hi @Dinu,

Thanks for your advice but as i mentioned i'm using CI/CD deploy pipper.

Could you please give me config for .pipeline/config.yaml to use MTA Descriptort?

[Dinu · Accepted solution]

Check parameters for cloudFoundryDeploy https://www.project-piper.io/steps/cloudFoundryDeploy/#mtaextensiondescriptor

[TinhLeo · Accepted solution]

hi @Dinu,

Thanks for the advice, i'm able to deal with it now.

Just have a mention i'm using mtaExtensionDescriptor  the cloudFoundryDeploy but see the docs https://www.project-piper.io/steps/cloudFoundryDeploy/#mtaextensiondescriptor see it's deprecated even i can use it for now.