You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This command would leverage deploy as a dependency, and possibly pipeline as well to support selection of a snapshot version.
Need to consider the simplest way for a user to provide their quay.io pull secret via the user.env file or other means.
This would be very similiar to startrhacm by @dhaiducek, except that it would include only the installation of ACM. Need to look at this project for inspiration and potential areas to re-use.
With this command, a cm user could obtain a new cluster and install ACM on it like so (options TBD):
cm new cluster-pool new-hub && cm install-acm new-hub
The text was updated successfully, but these errors were encountered:
Downstream is a straightforward curl since acm-custom-registry is open. (Check out the link for how I looped over all of the pages since curl only returns one page from Quay.)
Something to consider: I will say that while using Quay may be more straightforward since you can probably leverage the Quay token as you said, I think you'll lose the ability to distinguish between a stable and edge build specified in pipeline. But if you're upstream, perhaps that doesn't matter anyway. The tags in Quay will be easier to retrieve (just like the command above, which could probably be reused) since you wouldn't have to reconfigure the manifest filename into a tag like I'm currently doing in startrhacm (or maybe you'll find a cleverer way! 🙂 ):
This command would leverage deploy as a dependency, and possibly pipeline as well to support selection of a snapshot version.
Need to consider the simplest way for a user to provide their quay.io pull secret via the
user.env
file or other means.This would be very similiar to startrhacm by @dhaiducek, except that it would include only the installation of ACM. Need to look at this project for inspiration and potential areas to re-use.
With this command, a
cm
user could obtain a new cluster and install ACM on it like so (options TBD):The text was updated successfully, but these errors were encountered: