feat: add namespace arg when producing doc #588
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
hallyn
approved these changes
Jan 26, 2024
Currently, stacker-bom doesn't include namespace information in the document. Adding a cmdline arg to do so. Signed-off-by: Ramkumar Chinchani <rchincha@cisco.com>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #588 +/- ##
===========================================
+ Coverage 13.02% 57.15% +44.13%
===========================================
Files 40 64 +24
Lines 6059 7525 +1466
===========================================
+ Hits 789 4301 +3512
+ Misses 5138 2481 -2657
- Partials 132 743 +611 ☔ View full report in Codecov by Sentry. |
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.
Currently, stacker-bom doesn't include namespace information in the document. Adding a cmdline arg to do so.
What type of PR is this?
Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:
Automation added to e2e:
Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.