-
Notifications
You must be signed in to change notification settings - Fork 28
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: add the namespace flag #234
Conversation
@deewhyweb i think that might do it, mind giving a try |
This would actually be great. And removing the project will remove all of the various pods that are a part of it, in one fell swoop. |
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.
Other than a small nit, looks good to me.
bin/nodeshift
Outdated
@@ -74,6 +74,10 @@ yargs | |||
type: 'boolean', | |||
default: false | |||
}) | |||
.options('namespace', { | |||
describe: 'flag to specify the project namespace to build/deploy into. Overwrites the value from the config loader', |
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.
Does it make more sense to say something like, "Overwrites any namespace settings in your OpenShift of Kubernetes configuration files"? Not sure that's an improvement, but saying "the config loader" implies knowledge of nodeshift that the user might not have.
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.
that makes sense. will change
This allows the user to specify a namespace project during the build/deploy. Overwrites any namespace settings in your OpenShift or Kubernetes configuration files fixes nodeshift#233
4339d8f
to
c78337e
Compare
I'll give it a go today.
…On Fri, Jun 1, 2018 at 11:38 AM, Lucas Holmquist ***@***.***> wrote:
@deewhyweb <https://github.com/deewhyweb> i think that might do it, mind
giving a try
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#234 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABKd5H1pK0wr3ScurdECFnSNOD6ld2maks5t4V_ggaJpZM4UW5zM>
.
|
@deewhyweb thanks, i didn't actually do a new release yet. |
This allows the user to specify a namespace project during the build/deploy. Overrides the namespace that the config loader gets
fixes #233
This should do it. I am curios though, how easy would it be to have the project get created if the namespace that was specified didn't exist yet. probably could be another PR though
That could be interesting for Rhoaster, like, you deploy your app to a "temporary" namespace that gets created, then during the undeploy, it can get remove(or keep it around if you wanted to)