AIAP: Utilize document pull command for arbitrary refspecs
#623
Assignees
Labels
Milestone
Comments
ian-howell
added
enhancement
jezogwza
added
priority/medium
airshipbot
pushed a commit
that referenced
this issue
Sep 7, 2021
This causes the 22_test_configs.sh to create an airship config file which supports the new document pull feature introduced in https://opendev.org/airship/airshipctl/commit/cb080a20664196e61b0586b7ef7ecdb3a1090c88 Change-Id: I057bd2420f488a9f91ed69d09f73b1336827e7a2 Relates-To: #623 Change-Id: I7bbf052877e4918e168fc4005ea899aa700bae41
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description (if applicable)
We would like to be able to use AIAP with manifests other than the current upstream master gating site. As of cb080a2, We now have the ability to specify an arbitrary refspec for the
document pullcommand. I would like to be able to use that feature in AIAP so that I could test other manifests. This could be done by specifying a refspec as an environment variable passed into AIAP'srunnercontainer.Proposed change
Modify the AIAP
runnerscripts to insert a new variable (e.g.MANIFESTS_SITE) into the airshipctl config file'srepository.fetch.remoteRefSpecfield to be used bydocument pullThe text was updated successfully, but these errors were encountered: