Skip to content
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

Merged
merged 1 commit into from
Jun 1, 2018

Conversation

lholmquist
Copy link
Member

@lholmquist lholmquist commented Jun 1, 2018

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)

@ghost ghost assigned lholmquist Jun 1, 2018
@lholmquist
Copy link
Member Author

@deewhyweb i think that might do it, mind giving a try

@lholmquist lholmquist requested a review from lance June 1, 2018 15:38
@coveralls
Copy link

coveralls commented Jun 1, 2018

Coverage Status

Coverage increased (+0.02%) to 96.212% when pulling c78337e on lholmquist:233-specify-namespace into 5e7eb71 on bucharest-gold:master.

@lance
Copy link
Member

lance commented Jun 1, 2018

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)

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.

Copy link
Member

@lance lance left a 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',
Copy link
Member

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.

Copy link
Member Author

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
@ghost ghost removed the in progress label Jun 1, 2018
@lholmquist lholmquist merged commit 13e5316 into nodeshift:master Jun 1, 2018
@ghost ghost removed the review label Jun 1, 2018
@deewhyweb
Copy link

deewhyweb commented Jun 4, 2018 via email

@lholmquist
Copy link
Member Author

@deewhyweb thanks, i didn't actually do a new release yet.

@lholmquist lholmquist deleted the 233-specify-namespace branch January 2, 2019 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to specify project namespace when performing deploy
4 participants