btpsa-v1.2.1

[lechnerc77]

v1.2.1 (2022-12-08) 🎁

Bug Fixes 🐞

• [#357] - Propagation of errors for Cloud Foundry org role assignment
• [#359] - Skip CF space creation

Other Changes

• Regular update of btpsa-usecase.json and automated documentation due to updates in the service metadata
• Restructuring of documentation [#361]

---

This discussion was created from the release btpsa-v1.2.1.

[lechnerc77]

Details on "Propagation of errors for Cloud Foundry org role assignment"

The handling of errors when executing cf set-org-role had a bug and as a consequence error where not reported back (as shown in the screenshots above). It seemed like the assignment was executed successfully, but it was not.
PR #357 fixed this behavior; errors are now propagated and displayed correctly. However, as they are now shown, you might run need to adjust your configuration files in case an "Ambiguous user" is detected that has several (IdP) origins. You can do that as of release 1.2.0 as described in the announcement of release 1.2.0 i.e., Detail on "Support of custom IdPs in role assignment (incl. CF roles)".

Why don't we default to sap.idp? This would mean that existing working configurations might need to be adopted and we want to avoid this breaking change for existing users.

[lechnerc77]

Details on "Skip CF space creation"

To omit the creation of a CF space we provide a new parameter in parameters.json. If you want to skip the creation of a CF space although you create a CF environment (= org) you can set the parameter skipcfspacecreation to true.

The default value of the parameter is false, so all existing parameter.json configurations do not need to be adjusted

From great power comes great responsibility: there is no safety net in the btp-setup-automator concerning the overall consistency when you omit the creation of a CF space. There is no validation if a space is needed due to other configurations in your use case.