-
Notifications
You must be signed in to change notification settings - Fork 15
chore(implementations): add init --no-default-provisioners
flag description
#168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
chore(implementations): add init --no-default-provisioners
flag description
#168
Conversation
Converting as Draft for now because depending on score-spec/score-k8s#150. |
@mathieu-benoit, moving to ready for review since the PR has been merged |
Good point, seeing this CI error to fix please:
|
Signed-off-by: lekaf974 <[email protected]>
Signed-off-by: lekaf974 <[email protected]>
edcab12
to
4314bd5
Compare
changes pushed |
--no-default-provisioners
flag description
--no-default-provisioners
flag descriptioninit --no-default-provisioners
flag description
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lekaf974, let's do it for score-compose
too, right?
Now released too: https://github.com/score-spec/score-compose/releases/tag/0.27.1
did not remember if it has been done in score-compose ! |
Thank you for submitting this pull request! We appreciate you spending the time to work on these changes.
What is the motivation?
Update documentation based on changes done in score-k8s adding
--no-default-provisioners
flag in init commandWhat does this change do?
Provide a description of what this pull request does.
Add
--no-default-provisioners
flag descriptionWhat is your testing strategy?
Is this related to any issues?
Related to score-spec/score-k8s#148 and needs score-spec/score-k8s#150 to be merged
If this pull request is related to any other pull request or issue, or resolves any issues - then link all related pull requests and issues here.
Have you read the Contributing Guidelines?