-
Notifications
You must be signed in to change notification settings - Fork 112
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
Add a new extra variable for holding the update's parameters #1903
Add a new extra variable for holding the update's parameters #1903
Conversation
Thanks for the PR! ❤️ |
I like the change and idea for new cifmw_update_extras. Just can you rephrase description, please? The aim is to add cifmw_update_extras dict defined at zuul job definition level, instead of using pre-defined inline variables. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
o/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix example in description and you have LGTM from me.
Make sure that, when we use downstream repo setup we don't hardcode cifmw_repo_setup_promotion. To that end, and to add more flexibility to the variables that need to be overwritten during update, take the key/value of the `cifmw_update_extras` hash. It should be defined in a job and would look like this: ``` cifmw_update_extras: cifmw_repo_setup_promotion: promotion other_var: value ... ``` That enables the job definition to pass all variables needed for the update job with having new variable name for each override. It also solves the problem of the hardcoded `cifmw_repo_setup_promotion` as now the job has total control over the variables passed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
/approve |
@sathlan @ciecierski you need to harrass someone from this list https://github.com/openstack-k8s-operators/ci-framework/blob/main/OWNERS to add the /approve here for merge fyi |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: marios, pablintino The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
e6406f5
into
openstack-k8s-operators:main
Make sure that, when we use downstream repo setup we don't hardcode
cifmw_repo_setup_promotion.
To that end, and to add more flexibility to the variables that need to
be overwritten during update, take the key/value of the
cifmw_update_extras
hash. It should be defined in a job and wouldlook like this:
That enables the job definition to pass all variables needed for the
update job with having new variable name for each override.
It also solves the problem of the hardcoded
cifmw_repo_setup_promotion
as now the job has total control over thevariables passed.
Jira: https://issues.redhat.com/browse/OSPRH-7811
As a pull request owner and reviewers, I checked that: