Fix tags extraction from runtime config #2617
Merged
Conversation
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
Also bump up max supported and preferred cpi version to 3
beyhan
approved these changes
Jul 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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 is this change about?
These changes fix the way tags are extracted from the runtime config when creating a stemcell (the tags are then sent to the cpi).
Please provide contextual information.
Extend bosh tagging for cpi #2603
What tests have you run against this PR?
Unit tests and manual tests against a development environment.
How should this change be described in bosh release notes?
Fixes tag (for cpi on stemcell creation) extraction from the default runtime config.
Does this PR introduce a breaking change?
No
Tag your pair, your PM, and/or team!
@DennisAhausSAP, @a-hassanin