Skip to content

Releases: SAP/crossplane-provider-btp

v1.0.1

05 Dec 14:15
d737df4
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.0.0...v1.0.1

v1.0.0

04 Nov 14:18
d5f9b24
Compare
Choose a tag to compare

This is our first open-source release of the crossplane-provider-btp.

Breaking Changes to previous (internal) versions

Changed API group and hierarchy: We changed the API Group of all CRDs and moved some CRDs to a different domain in the group.
The following reflects the changes in the API group, for a migration script, see below[1]:

CloudManagement, Directory, DirectoryEntitlement, Entitlement, GlobalAccount (deprecated), ServiceManager, Subaccount, Subscription:

Old Group New Group
account.btp.orchestrate.cloud.sap account.btp.sap.crossplane.io

ProviderConfig, ProviderConfigUsage, ResourceUsage, StoreConfig (change in group hierarchy):

Old Group New Group
account.btp.orchestrate.cloud.sap btp.sap.crossplane.io

CloudFoundryEnvironment, KymaEnvironment:

Old Group New Group
environment.btp.orchestrate.cloud.sap environment.btp.sap.crossplane.io

CertBasedOIDCLogin, KubeConfigGenerator:

Old Group New Group
oidc.btp.orchestrate.cloud.sap oidc.btp.sap.crossplane.io

GlobalaccountTrustConfiguration, RoleCollectionAssignment, RoleCollection, SubaccountTrustConfiguration:

Old Group New Group
oidc.btp.orchestrate.cloud.sap oidc.btp.sap.crossplane.io

What's Changed

  • Finalizing the open-sourcing of the provider by @enrico-kaack-comp in #4
  • chore: update env vars to use latest tf provider version by @sdischer-sap in #12
  • fix: subaacount label update/delete by @elle-le in #16
  • Bump github.com/docker/docker from 25.0.0+incompatible to 25.0.6+incompatible by @dependabot in #2

New Contributors

Full Changelog: https://github.com/SAP/crossplane-provider-btp/commits/v1.0.0

Appendix

[1] Migration Script
This script should act as guidance for you to change the api groups from previous versions to this open-source version.
The script assumes you have the CR in yaml files on your filesystem, one CR per file.
Make sure you backup your files first!!!
Adapt this script to your needs.

#!/bin/bash

####
# This script will find all yaml files recursivly in the given directory and replace the group.
# For ProviderConfig, ProviderConfigUsage, ResourceUsage and StoreConfig the hierarchy changed from account.* to root level, this is handled in the if-else block.
# !!! Create a backup of your files before using it !!!
####

# Check if the file path is provided
if [ -z "$1" ]; then
echo "Usage: $0 <directory-path>"
exit 1
fi

# Get the directory path
DIR_PATH=$1

# Loop over all the YAML files in the directory and subdirectories
find "$DIR_PATH" -type f  \( -name "*.yaml" -o -name "*.yml" \) | while read -r FILE; do
# Check if the file contains the kind that require a change in group hierarchy
if grep -q -e "ProviderConfig" -e "ProviderConfigUsage" -e "ResourceUsage" -e "StoreConfig" "$FILE"; then
# Change the hierarchy from account.... to root level
sed -i -e 's/account\.btp\.orchestrate\.cloud\.sap/btp\.sap\.crossplane\.io/g' "$FILE"
else
# Replace the root domain of the group
sed -i -e 's/btp\.orchestrate\.cloud\.sap/btp\.sap\.crossplane\.io/g' "$FILE"
fi
done