Add vendor_data2 support for ConfigDrive source#1307
Merged
Conversation
TheRealFalcon
approved these changes
Mar 9, 2022
Contributor
TheRealFalcon
left a comment
There was a problem hiding this comment.
Thanks for contributing to cloud-init!
This PR looks good to me. CI never returned from Travis, so I'm going to close and re-open this PR to re-trigger CI. If that passes then we should be good to merge.
This was referenced May 12, 2023
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
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.
Proposed Commit Message
Test Steps
Generate a OpenStack configuration drive that contains vendor_data2.json and verify the context of the JSON file are properly executed.
Checklist: