fix issue #49938: missing property in helm airbyte/value.yaml (helm v1.3.1) #392
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
there is a somewhat "breaking" change introduced by this commit. 02e3c97
I'm not sure the context of this commit, but as far as I understand,
global.serviceAccountName
should be used across each services in airbyte.however, if the purpose is to let "workload-launcher" to use its own serviceaccount, then
airbyte/values.yaml
should be updated because this is where most end-users refer to since there is no changelog for helm charts.How
to fix this issue airbytehq/airbyte#49938
Recommended reading order
value.yaml
Can this PR be safely reverted and rolled back?