Recent enhancements of the btp-setup-automator

[lechnerc77]

Over the last weeks quiet some improvements have reached the btp-setup-automator. In this post we want to shortly summarize our main new features and bug fixes that are available as of today:

• Service creation/deletion - logging: The creation and deletion of service instances can take some time. The setup-automator often has to wait for this in order to continue with the overall setup process. The logging that was exposed to the user could be confusing and might be interpreted as an endless loop. We have enhanced the logging and made it a chattier so that the user has a better idea what is happening. For details see issue [FEATURE REQUEST] Confusing looging when service creation/deletion is checked #265 and PR Extended logging #266.
• CF extension landscapes: Up to now the btp-setup-automator did not take into account CF extension landscapes. This could lead to issues with the CF API endpoint (see issue [BUG] Error authenticating CF instance (wrong CF API endpoint) #257) and you also had no option to specify the landscape (which is possible in the SAP BTP cockpit - see issue [FEATURE REQUEST] Need to select which endpoint CF is deployed to #274). Both points are now included in the btp-setup-automator (see PRs Identification of CF API Endpoint #259 and Feature: Specification of CF landscape when creating CF org #275).
• Creation of directories and assignment of subaccounts: the btp-setup-automator did not support directories up to now (see issue [FEATURE REQUEST] Automate creation of sub-account within a directory #272). We enabled this functionality with PR Enhancement - Support of Directories #279. Be aware that we started with a basic support of that feature as described in the PR.
• Custom role collections: Although the assignment of existing role collections to user groups was supported since quite a while (see issue Improved handling of users and role collections #119). It was not possible to create a new custom role collection. This feature is now available see PR Custom Role Collections and role assignment #273.
• Documentation: one gap in the documentation was the comprehensive documentation of the parameters available in the usecase.json and the parameters.json file. This was compensated by backing the files via a JSON schema, but the flexibility is too high to rely on that. With PR Improvement of documentation  #282 and Finalization of docu generation #283 we have now an autogenerated documentation available in the repository. This still has some rough edges, but the generated markdown files give you a good overview what options you have.
• Build of Docker Image on WSL2: we had a bug in the Docker image build on Windows in WSL2 (see issue [BUG] Container Build fails on WSL - home directory not created? #248). This was fixed and frictionless usage of the btp-setup-automator with WSL2 is possible.