Fix broken ProviderConfig schema in extension-provider-aws#687
Merged
Bobi-Wan merged 2 commits intogardener:mainfrom Nov 5, 2025
Merged
Conversation
gardener-robot
added
needs/review
…et fix for breaking spec Bug: While strict decoding a providerConfig (defined in aws extension), we encounter a field name change (capabilitySets -> capabilityFlavours). Even though we don't use it, the strict decoder fails and reports an error. PR breaking the current functionality: gardener/gardener-extension-provider-aws#1480 Fix: bump to provider extension aws, so the expencted cloudprofile.spec.providerconfig has the same schema as the ones in the dev landscape.
Bobi-Wan
force-pushed
the
fix/provider-aws-broken-providerconfig
branch
from
337ac9e to
65075d2
Compare
gardener-robot
added
reviewed/lgtm
gardener-robot
added
the
status/closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Fixes the following bug:
Bug:
While strict decoding a providerConfig (defined in aws extension),
we encounter a field name change (capabilitySets -> capabilityFlavours).
Even though we don't use it, the strict decoder fails and reports an error.
PR breaking the current functionality:
gardener/gardener-extension-provider-aws#1480
Fix:
Bump to provider extension aws, so the expencted
cloudprofile.spec.providerconfig has the same schema as the
ones in the dev landscape.
Dependency changes all come from
Special notes for your reviewer:
I am expecting something similar to pop up in other extensions as well,
as the change is triggered by a public API change in gardener/gardener:
gardener/gardener-extension-provider-aws#1480
Release note: