Releases: cap-js/cap-operator-plugin
Releases · cap-js/cap-operator-plugin
v0.16.1
v0.16.0
Added
- Added
SubscriptionDependencyModesupport (Auto,Always,Never) toserviceInstancesinvalues.schema.json. - Added
startupProbefield to workload definitions invalues.schema.json. - Updated build step to be more flexible and support user-defined templates (#103)
Changed
- Updated
getDependenciesanddependenciesCallbacksURLs inruntime-values.yamlto use the CAP Operator-managed endpoints (/dependencies/{{providerSubaccountId}}/{{appName}}), replacing the previous approuter callback URLs. Use this version with CAP Operatorv0.29.2or later. - Removed optional mutual TLS (
OptionalMutual) configuration; TLS mode is now always set toSimple. - Removed
sme.sap.com/vs-route-request-header-set(x-forwarded-client-cert) annotation from CAPApplication templates. - Improved validation logic for
appNamefield duringruntime-values.yamlgeneration. - Simplified
Durationtype invalues.schema.jsonfrom a nested object to a plain string.
v0.15.0
Changed
- Deprecated
globalAccountIdin favor ofproviderSubaccountIdin thevalues.yamlfile. This change is part of the latest CAP Operator versionv0.28.0. Use this version with CAP Operatorv0.28.0or later to avoid any compatibility issues. - Defaulting
ttlSecondsAfterFinishedto 300 seconds for job workloads. - Added
sme.sap.com/enable-cleanup-monitoring: "true"as a default annotation on the CAPApplication resource. serviceExposuresrestriction removed in from CAPApplicationVersion template to allow users to configure it as per their needs.- Updated
values.schema.jsonto align with the latest CAP Operator versionv0.28.0and BTP Service Operator versionv0.10.5. - Replaced
readlinebased prompt withenquirerfor improved interactive prompt experience during runtime values generation. Required fields are now marked with*and validated inline.
v0.14.0
Added
- Added new mandatory parameter
providerSubaccountIdto thevalues.yaml. Required for application identification during subscription asglobalAccountIdwould be deprecated in future. - Dependencies updated.
v0.13.0
Added
- Updated
values.schema.jsonto support CAP Operatorv0.24.0and BTP Service Operatorv0.10.0.
Changed
- Improved MTA transformer:
TENANT_HOST_PATTERNis no longer added to Router workload invalues.yaml(handled by the template)redirect-urisremoved from xsuaaoauth2-configuration(computed dynamically inservice-instance.yamltemplate)- Router workload now includes all service bindings in
consumedBTPServicesto supportgetDependenciescallback
v0.12.1
Fixed
- Updated the mta transformer to handle optional path attributes in the mta.yaml file correctly.
v0.12.0
Added
- Updated workload environment variable handling in
runtime-values.yaml. Only add env to workload if the user provides hana instance ID during generation.
v0.11.0
Added
- Updated
values.schema.jsonto align with the latest CAP Operator versionv0.23.0and BTP Service Operator versionv0.9.4. - Dependencies updated.
v0.10.0
Added
- Added support for IAS and AMS based subscriptions.
- Template generation refactored to use common template functions for better maintainability.
v0.9.0
Fixed
- Removed redundant
oauth2-configuration.redirect-urisandTENANT_HOST_PATTERNfrom the generatedruntime-values.yamlfile as it is now handled in the corresponding templates.