-
Notifications
You must be signed in to change notification settings - Fork 43
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
feat: support validating and installing provisioner files by uri #175
Conversation
Signed-off-by: Ben Meier <[email protected]>
4a02575
to
52915fa
Compare
Signed-off-by: Ben Meier <[email protected]>
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.
In one file, we could have multiple provisioners
per se, so should it be --provisioners
in plural instead of --provisioner
?
Signed-off-by: Ben Meier <[email protected]>
@mathieu-benoit good point, fixed up and added a test :) |
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.
Small updates/questions.
Signed-off-by: Ben Meier <[email protected]>
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.
LGTM
Installing provisioners by copying yaml files around is not a great UX and makes things unecessarily multi-step.
This PR improves this by adding a
--provisioners <URI>
flag which downloads a provisioner file using either http, git, or local filesystems and adds it into the .score-compose state directory at the top of the stack.