Releases: SAP/component-operator-runtime
v0.3.149
v0.3.148
What's Changed
🚀 New Features
- scope PAT-using release/publish jobs to 'release' environment (f7a5f5c)
- scope publish workflow jobs to 'release' environment (23990ea)
🔧 Improvements
- declare explicit permissions for read-default rollout (d342fab)
- declare explicit permissions for read-default rollout (a7ab384)
Full Changelog: v0.3.147...v0.3.148
v0.3.147
What's Changed
🐛 Bug Fixes
🔧 Improvements
- update dependency postcss to v8.5.15 (#434) (2734c55)
- update actions/stale action to v10.3.0 (#435) (f6f1fb8)
Other Changes
- update .github/workflows/stale-issue-pr.yaml (4a43467)
- Fix typo in ready condition value ReadyConditionReasonRetrying (#429) (cf94a5c)
- add subcommand clm template (#437) (e058bfa)
Full Changelog: v0.3.146...v0.3.147
v0.3.146
What's Changed
🐛 Bug Fixes
Other Changes
- update .github/workflows/stale-issue-pr.yaml (17804d4)
Full Changelog: v0.3.145...v0.3.146
v0.3.145
v0.3.144
v0.3.143
v0.3.142
Enhancements
Support for Post Renderers
Two new object transformers are provided now by this package:
type SubstitutionObjectTransformer struct {
// ...
}
var _ ObjectTransformer = &SubstitutionObjectTransformer{}
func NewSubstitutionObjectTransformer(substitutions map[string]string, selector types.Selector[client.Object]) and
type KustomizeObjectTransformer struct {
// ...
}
var _ ObjectTransformer = &KustomizeObjectTransformer{}
func NewKustomizeObjectTransformer(patches []KustomizePatch, images []KustomizeImage) (*KustomizeObjectTransformer, error)Consumers can re-use these transformers to provide post-build variable substitution and kustomize-based post-rendering.
Support for suspending components
Sometimes it is desired to temporarily suspend the reconciliation of a component. In order to provide this, components (or their spec) can implement the interface
type SuspensionConfiguration interface {
IsSuspended() bool
}In that case, if the method IsSuspended() returns true, the component will go into Pending state (with Ready reason Suspended), and no further reconciliation will happen until the suspension is removed. Note that suspension does not affect deletion of the component. That is, if a suspended component gets deleted, the deletion is performed as usual.
For easier consumption, components can embed the re-use type SuspensionSpec into their spec.