btpsa-v1.7.0

[lechnerc77]

v1.7.0 (2023-03-29)

New Features and Enhancements 🚀

• [#467] - Update UseCase file for btp-resilient-apps repo - event mesh changes + entitleonly param usage
• [#468] - Enhancement of role collection assignment with custom IdP.

Bug Fixes 🐞

• [#470] - Fix NoneType Error during app subscription.
• [#472] - Read subaccount domain from existing subaccount
• [#473] - Fix issue inappropriate ioctl for device with multiple CF spaces in a subaccount.

Other Changes

• [#466] - Update version of BTP CLI to 2.38.0.
• Regular update of btpsa-usecase.json and automated documentation due to updates in the service metadata including the latest naming changes introduced by SAP Build
• Dependabot updates of dependencies

Community Contributions

@AlexRieder , @maxstreifeneder

---

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

[lechnerc77]

Limitation Details

In the context of issue 471 and the fix in PR 473, be aware of the following restrictions:

• if using sso for authentication you will not be able to create a new Cloud Foundry space in a SAP BTP sub account that already contains Cloud Foundry spaces. Reason for this is that we must use the cf login command of the CF CLI to execute the login via SSO. As cf login is a bracket around several CF CLI commands an interactive entry of a CF space name needs to be done if more than one CF space is already existing in the SAP BTP sub account. This will cause an error (inappropriate ioctl for device) and the script will abort. This is an issue within the CF CLI and not with the BTP Setup Automator
• if using username and password for the authentication, we switched the authentication flow to the CF commands that allow a non-interactive authentication, namely a sequence of cf api, cf auth and cf target. Using this authentication flow will allow you to execute the BTP Setup Automator in SAP BTP sub accounts with more than one Cloud Foundry space.