Welcome to btp-setup-automator Discussions!

[rui1610]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[aliedl0424]

Greetings! Alex Liedl from Cargill. We are just getting started on our BTP journey and my goal is to embed automation from day 1. I came across the btp setup automator and am intrigued. Still havent gone through all the documentation or dig through all the included scripts but any thoughts on how we could tailor or create scripts for basic BTP operational activities such as creating a subaccount, managing users/role collections, trust settings, setting entitlements, subscribing to services, etc. My goal is to have all of this documented in a state file somewhere similar to how we would manage infra with a tool such as terraform. Thoughts?

[yevgentrukhin]

Hi Alex, the tool can do exactly what you described and the state is kept in usecase.json files. You would need to study a bit sample use case files to see how you can tailor them towards your usecase, check this one, for example: https://github.com/SAP-samples/btp-setup-automator/blob/main/usecases/released/extendS4_with_devops.json
Best Regards, Yevgen

[rui1610]

Checkout the documentation providing you a step-by-step explanation:

https://github.com/SAP-samples/btp-setup-automator/tree/main/docs/README.md

[rui1610]

Hey @aliedl0424 , where you successful in getting started with the script? Interested to understand how you are using it and whether it is useful to you at all.

[aliedl0424]

Hey thanks for reaching out! So I took a look at the scripts included. I see the potential. That said, I see it not quite meeting my requirements. Ideally I am looking for something like terraform that would be able to not only deploy resources but also manage the state (i.e. check to see if tf script has resources already provisioned in the tf.state file). At this point in our journey, i am not necessarily looking for a means to deploy resources for full stack applications but rather purely on the BTP platform operations (i.e. setting up sub accounts, enabling principle propagation, assigning users and authorizations, setting up destinations, etc). I believe that the scripts could do this but i also see that there would be quite some python reverse engineering required. That said, if you are able to provide a really simple example of one of the use cases mentioned above, it may help me in my thought process. I also heard that you may be working on terraform support and may have some preliminary successes? Would be really interested in learning more/partnering.

…

On Thu, May 12, 2022 at 7:37 AM Rui Nogueira ***@***.***> wrote: Hey @aliedl0424 <https://github.com/aliedl0424> , where you successful in getting started with the script? Interested to understand how you are using it and whether it is useful to you at all. — Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETAUSAQ2B3N7BM3A6XTLNTVJT3PNANCNFSM5Q6YBOMA> . You are receiving this because you were mentioned.Message ID: <SAP-samples/btp-setup-automator/repo-discussions/20/comments/2737527@ github.com>

[rui1610]

Did you have a look into the released usecase files? The documentation should help you as well to get up-to-speed on the btp-setup-automator.

[dachtera]

Hello all,

My team is working on building out our BTP automation for creation of sub-accounts and we're running into a few issues.

1. There is a discrepancy between the entitlements and options available within the UI, and those available when creating your JSON file (Such as Cloud Foundry, Launchpad to name a few of our core services)

2. Difficulty adding multiple plans in the JSON file, when it's possible within the UI.

Example below of a service available within the UI, but not the automator:
ERROR : service >saplaunchpad< with plan >standard< in region >eu10< IS NOT AVAILABLE

Our end goal is to have an end-to-end process to add in all of the entitlements/options etc for a sub-account without manual updates after the fact.

Can I connect with someone with deeper experience in the scripting and learn more how/why we're running into discrepancies and how to overcome them?

Thank You.

[rui1610]

The name of the service is wrong. It is case sensitive and is called SAPLaunchpad

[rui1610]

You can simply remove the entry for cloudfoundry. Should work as well.

[dachtera]

Interesting on the cases, as I'm using VS Code with type-ahead enabled. Seems to be an issue there. Actually, earlier in the week when I was manually keying everything SAPLaunchpad was throwing an error about now being available but processes now ( keeps looping this now for 10 minutes and counting)

[2022-10-13 15:48:36] INFO       : check status of app subscriptions
[2022-10-13 15:48:36] RUN COMMAND: btp --format json list accounts/subscription --subaccount '07f9e26d-ed9d-44e8-bcb4-8d19c9da3aaa'

CloudFoundry is a requirement for our team, as well as creating the space and assigning the org members. If the Automator is not capable of completing these tasks, it's not terribly useful to our team.

Would it be wise of me to setup a meeting with someone to help determine what is my mistake and what is truly a bug/issue? I don't want to clutter up things by submitting a bunch of issues, if it's a quick fix to my JSON.

[rkapoz-bgp]

You can simply remove the entry for cloudfoundry. Should work as well.

Hi rui1610,
I'm starting using and testing this automation tool; I noticed a strange thing about services that the automation provision: the automation provision CF even is not explicitily referenced in the list of services to be provisioned. May be the case other defined services that depend on CF will cause CF to be provisioned anyway?

[lechnerc77]

@dachtera: I will try to split your questions into dedicated units:

• "SAPLaunchpad"-topic: The naming/type ahead support was a bit shaky due to a switch in the internal fetching of the information. This was fixed and should be stable now.
• Creation of Cloud Foundry spaces: You can create Cloud Foundry spaces, indeed this is the default behavior. As you can see in the parameters.json you can specify e.g. the org id, org name and the space name that should be created and/or used for the service creation.
• "Infinite loop in entitlements"-topic: The entitlement of application contained a bug which caused this behavior. It was fixed via PR app subscription fix #258. A new Docker image containing the fix is available.
• Setup: The desired target setup you described in this discussion works and is described in issue Issue with cloudfoundry service in usecase.json #255 (including sample files). The created Cloud Foundry environment contains only the person specified in the email field of the parameters.json as Org Manager.
• Adding members to Cloud Foundry in different roles: If you want to add additional members in different roles you need to specify them in the parameters.json via "usergroups". You can define several user groups. These groups must then be referenced in the usecase.json file. You find a sample in the file cf_cups.json under usecases/released.
• Connection Service and Environment: The connection between services and environments is defined by the optional field "targetenvironment" that you can define per service. The default value is Cloud Foundry, but you can also create services in Kyma (which comes with the prerequisite that the kubeconfig.json is available in the container) and services for the environment "others" (as in the SAP BTP Cockpit) which will then have no binding to any environment. The same is true for service bindings.

Hope that helps

P.S. in order to keep the discussion a bit better manageable, please open dedicated question in the discussions area via starting a new discussion and selecting the category "Q&A"

[aliedl0424]

I would also love to be involved if there is a session on this.

…

On Wed, Oct 12, 2022 at 8:55 AM Tim Dachtera ***@***.***> wrote: Hello all, My team is working on building out our BTP automation for creation of sub-accounts and we're running into a few issues. 1. There is a discrepancy between the entitlements and options available within the UI, and those available when creating your JSON file (Such as Cloud Foundry, Launchpad to name a few of our core services) 2. Difficulty adding multiple plans in the JSON file, when it's possible within the UI. Example below of a service available within the UI, but not the automator: ERROR : service >saplaunchpad< with plan >standard< in region >eu10< IS NOT AVAILABLE Our end goal is to have an end-to-end process to add in all of the entitlements/options etc for a sub-account without manual updates after the fact. Can I connect with someone with deeper experience in the scripting and learn more how/why we're running into discrepancies and how to overcome them? Thank You. — Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETAUSD3ZQPJHIYOGTW6FBDWC27N3ANCNFSM5Q6YBOMA> . You are receiving this because you were mentioned.Message ID: <SAP-samples/btp-setup-automator/repo-discussions/20/comments/3860894@ github.com>

[dachtera]

The enablement for cloud foundry in the automation is a requirement. Simply removing it will not meet the requirements to have it added during automation. Is there a second round of activations to take place after the initial sub account is created? I may really need to get on a call with someone to show our current environment and requirement for automation as I need to answer to my leadership on this process. Thank You, Tim Dachtera | CTE Consultant III | SAP Concur ***@***.******@***.***> | 952-697-2942 / 507-298-5355 | MN60 – Minnesota, US On Oct 15, 2022, at 3:58 AM, Roberto Capozzo ***@***.***> wrote:  You can simply remove the entry for cloudfoundry. Should work as well. Hi rui1610, I'm starting using and testing this automation tool; I noticed a strange thing about services that the automation provision: the automation provision CF even is not explicitily referenced in the list of services to be provisioned. May be the case other defined services that depend on CF will cause CF to be provisioned anyway? — Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSAP-samples%2Fbtp-setup-automator%2Fdiscussions%2F20%23discussioncomment-3884285&data=05%7C01%7Ctim.dachtera%40sap.com%7C1058ed5b9146472d912608daae8b5a07%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638014210800625578%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Arfsa16uf6BUm6Wq6H2SqWjSG6HCAwURAn0Nrb2vDeU%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA3SIOCEIEXJW2UFJEFZUX7LWDJWZHANCNFSM5Q6YBOMA&data=05%7C01%7Ctim.dachtera%40sap.com%7C1058ed5b9146472d912608daae8b5a07%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638014210800625578%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2Boovjyj5mOrfxHWHHq911rCFJpW4flm5S05jUO%2F57YI%3D&reserved=0>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[lechnerc77]

See my answers above #20 (reply in thread)