Allow vendoring into nnf-integration-test repo #231
Merged
Conversation
This file contains 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
Adjust vendor-new-api.py so it can vendor into the nnf-integration-test repo. This relies on a new crd-bumper.yaml file in that repo to give some hints. Refactor code that checks whether an API is a hub or a spoke. Refactor code that references the crd-bumper.yaml file. This simplifies the use of the object that holds the content of that file. Reformat code with 'black'. Signed-off-by: Dean Roehrich <[email protected]>
roehrich-hpe
requested review from
ajfloeder,
matthew-richerson and
bdevcich
|
This relies on NearNodeFlash/nnf-integration-test#89 when vendoring into the nnf-integration-test repo. |
matthew-richerson
approved these changes
Nov 15, 2024
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.
Adjust vendor-new-api.py so it can vendor into the nnf-integration-test repo. This relies on a new crd-bumper.yaml file in that repo to give some hints.
Refactor code that checks whether an API is a hub or a spoke.
Refactor code that references the crd-bumper.yaml file. This simplifies the use of the object that holds the content of that file.
Reformat code with 'black'.