Adding Automation Hub deployer with EE and repo sync #181
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes job templates to deploy an Automation Hub instance via the OpenShift operator, synchronize EE registries, and galaxy collections, and a workflow chaining them together. I created a custom credential type,
Usable Automation Hub Credentialsince we are not able to use the built-in credential types (Ansible Galaxy/Automation Hub API Token, orContainer Registry) within a playbook. This credential needs to be filled out by the user before running the relevant jobs.A distinguishing feature is that we use
ReadWriteOncefor the underlying PV (see OCP access modes ) as opposed to the recommendedReadWriteMany. Thus this should not be used for production system.It's also noteworthy that due to syncing ~2100 collections in the
rh-certifiedrepo and roughly 70GB of storage they occupy, the workflow takes ~30 minutes to run.This PR is a stepping stone to ultimately being able to have a relatively simple job within APD that builds a custom EE.