-
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
unbuild command? #190
Labels
Comments
|
Would it be useful maybe to have |
i think having that flag for undeploy might be how i go. i'll try that out first and see how it feels |
lholmquist
added a commit
to lholmquist/nodeshift
that referenced
this issue
Feb 21, 2018
…ds, buildConfigs and Imagestreams fixes nodeshift#190
lholmquist
added a commit
to lholmquist/nodeshift
that referenced
this issue
Feb 21, 2018
…ds, buildConfigs and Imagestreams nodeshift undeploy removeAll fixes nodeshift#190
lholmquist
added a commit
to lholmquist/nodeshift
that referenced
this issue
Feb 21, 2018
…ds, buildConfigs and Imagestreams nodeshift undeploy removeAll fixes nodeshift#190
ghost
removed
the
in progress
label
Feb 21, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we have undeploy, this removes the application specific stuff that gets created during the apply-resource goal.
We don't have anything currently exposed that will remove the buildConfig, builds and Imagestreams that we create during the build phase.
there is the
build.recreate
option that a user can pass in to remove builds/imagestreams, but a build is run after that.This would be more a method for our integration test framework, rhoaster. The code is there to delete these things, but it is inside of the build and imagstream files. We would need to break that out into its own thing perhaps.
I don't really like the name "unbuild" so i'm open to suggestions.
The text was updated successfully, but these errors were encountered: