Details
-
Task
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
False
-
-
False
Description
Problem Description:
galaxy-importer calls `ansible-test sanity` in 3 ways
- Use galaxy-importer's image on quay via openshift job in CRC
- Use galaxy-importer's image built in real-time when calling importer from the command line
- Use image provided by ansible-test by calling`ansible-test sanity --docker`
With #2 using `docker build` this is more complex to maintain, not normally expected of a tool like galaxy-importer, and when we update galaxy-importer's image it requires more time for each update. We also use a slightly modified Dockerfile so the images used are not consistent in #1 and #2.
Proposed Solution:
Use galaxy-importer's image on quay when calling importer from the command line. First the quay repository quay.io/cloudservices/automation-hub-ansible-test will need to be made public.
Attachments
Issue Links
- relates to
-
AAH-412 Have local and cloud ansible-test sanity use the same quay base image
- Backlog