Releases: openmcp-project/project-workspace-operator
Releases · openmcp-project/project-workspace-operator
Release v1.1.0
Changes included in v1.1.0:
Release v1.0.2
Changes included in v1.0.2:
🐛 Fixes
- correctly apply webhook configurations #145
- [USER][BUGFIX] correctly apply webhook configurations
Release v1.0.1
Changes included in v1.0.1:
🐛 Fixes
- specify crds path #143
- [DEVELOPER][BUGFIX] Add missing crds path
Release v1.0.0
Changes included in v1.0.0:
🔧 Chores
- make PWO v2-compatible #132
- [OPERATOR][BREAKING] When using PWO as a platform service, the configuration has to be provided as a
ProjectWorkspaceConfigcustom resource with the same name as thePlatformService. Webhook configuration which was provided via flags for the v1 deployment has been moved into this resource too. No changes to an existing v1 deployment are required. - [OPERATOR][FEATURE] The PWO can now be run as a v2 platform service. Note that a non-standard
platformservicesubcommand is required,task platformservicecan be used to generate a manifest that uses the currently checked-out version as image tag. Existing v1 instances of the PWO don't need any changes when updating to a version containing the new v2 logic. - [OPERATOR][FEATURE] The configuration has been extended and now takes additional resources users should have permissions for in projects and/or workspaces.
- [OPERATOR][BREAKING] When using PWO as a platform service, the configuration has to be provided as a