feat(cmd/push): parse requirements and deps from rulesfile #467
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
When the user does not provide requirements and dependencies when pushing a rulefile artifact, it will try to parse the rulefile and automatically set them in the config layer. It only supports files in .yaml format. Signed-off-by: Aldo Lacuku <aldo@lacuku.eu>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alacuku, FedeDP The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM label has been added. Git tree hash: 3a97df151ba971879533903f985d152bf6a5b070
|
|
/milestone v0.8.0 |
This was referenced Mar 21, 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.
When the user does not provide requirements and dependencies when pushing a rulefile artifact, it will try to parse the rulefile and automatically set them in the config layer. It only supports files in .yaml format.
What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area cli
/area tests
What this PR does / why we need it:
feat(cmd/push): parse requirements and deps from rulesfile
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: