-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
oc create should support creating buildconfigs #14138
Comments
this is going to require a huge number of flags to be useful (even worse than new-build/new-app today).... can you give me a use case for why new-build/new-app are not the right answer? |
Simplicity of usage, I want to create BC and only that, without any other accompanying resources. I don't want to create BC by hand because I don't remember the yaml structure and I'm lazy to do it everytime I want to create a BC. With reasonable flags I should be able to create a sketch of a BC with |
i disagree that this is possible with anything less than a half dozen flags. for a minimal buildconfig you need:
i'll create the card, but i'm worried we're just creating another version of new-app where every person who goes to use it is going to come back and say "can you add a flag so i can specify X on my buildconfig? i don't want to edit it afterwards". |
trello'd https://trello.com/c/vqI6QomG |
From what you've pointed out is just 4 flags where source repo is the required param. By definition |
they're all required parameters. just the source repo is not sufficient for us to do anything. And it's 6 flags because for flag (2) and (3) we either need: --from-image-stream/--from-docker-image or --from-image --as-imagestream/--as-dockerimage or some other disambiguation as to whether the user is pointing us to a docker image, or an imagestream, for both the --to and --from fields. Otherwise you get into the searching/matching/guessing madness that new-app currently does. Unless you're proposing that when creating a buildconfig you can only reference imagestreams (or only reference dockerimages). |
Only docker images, if you care about IS you'd use |
that seems silly. I don't want to introduce a command that creates buildconfigs that follow a structure we'd never recommend. imagestreams are the right tool for the job. Buildconfigs that don't use imagestreams are painful:
|
The most likely combination is: from a docker image |
Our
oc create
supports several resources, but no buildConfigs, as of yet. The only CLI for creating BC isoc new-app
oroc new-build
which aside from the BC creates a few additional resources.The text was updated successfully, but these errors were encountered: