-
Notifications
You must be signed in to change notification settings - Fork 109
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
mirroring and builds v1 #58
Comments
Gabe, could you please provide details about the interaction points which lead to this? |
Sure @sbose78 ... so again I've captured the more novel things in So you have
I have no idea what the level of support for mirroring is with the other build tools besides |
According to @sbose78 we have api fields to supply/override the command line parameters supplied to the image building command (whether it is buildah, buildpacks, kaniko, etc.) https://github.com/shipwright-io/build/master/pkg/apis/build/v1alpha1/Fbuild_types.go But the reconciler/controller does not yet process whatever fields exist. A possible MVP line that would be to complete the loop on this, and in this way, buildah users would have a path for supplying Then, items |
A more detailed rationale available here |
Most likely we will open up a new feature around parametrization. And @sbose78 is going to bring this up in the community meeting. |
My understanding is that an strategy can be extended to support any params we want to define for the tooling, e.g. |
The discussion on |
thanks @sbose78 closing this out |
today openshift build v1 can build registries.conf files with associated auth and certs to ensure they are available to the build process and its invocation of buidah
ultimately buildv2 should have some form of this
it very well might make sense for DEVEX to help abstact out logic used for build v1 for use by buildv2 .... https://github.com/gabemontero/obu is a prototype of such an endeavor
Update by shoubhik
If #537 takes care of this use case, we should document how to use the same to accomplish this use case
The text was updated successfully, but these errors were encountered: