-
Notifications
You must be signed in to change notification settings - Fork 46
Add a no-galaxy-force option #44
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
Conversation
main.go
Outdated
| Usage: "prepend paths to module library", | ||
| EnvVar: "PLUGIN_MODULE_PATH", | ||
| }, | ||
| cli.BoolFlag{ |
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.
- cli.BoolFlag{
- Name: "no-galaxy-force",
- Usage: "don't force overwriting an existing role or collection",
- EnvVar: "NO_GALAXY_FORCE",
+ cli.BoolTFlag{
+ Name: "galaxy-force",
+ Usage: "don't force overwriting an existing role or collection",
+ EnvVar: "PLUGIN_GALAXY_FORCE",
main.go
Outdated
| Tags: c.String("tags"), | ||
| ExtraVars: c.StringSlice("extra-vars"), | ||
| ModulePath: c.StringSlice("module-path"), | ||
| NoGalaxyForce: c.Bool("no-galaxy-force"), |
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.
GalaxyForce and galaxy-force
plugin.go
Outdated
| Tags string | ||
| ExtraVars []string | ||
| ModulePath []string | ||
| NoGalaxyForce bool |
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.
Same here
plugin.go
Outdated
| "--force", | ||
| } | ||
|
|
||
| if p.Config.NoGalaxyForce == false { |
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.
Same here
|
I forgot the |
|
BoolTFlag defaults to true. |
|
My bad. I fixed it. |
|
The CI reached docker hub pull rate limit but it should be fine now (11h later). If someone with the appropriate permissions could restart the build to get this merged. |
|
CI fail is fine as like you said it is due to docker hub rate limits, the other tests pass. Although if you want to trigger a build you could send an empty commit. |
|
Thanks for you effort! |
Related to #43.
This add the possibility to remove the
--forcetag during galaxy install. The end goal is to allow caching of galaxy packages.