Change how tempest is configured in test_operator role #2338
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
cjeanner
force-pushed
the
test_operator/config-override
branch
from
a730465
to
bb725c3
Compare
Until now, whenever someone wanted to add a new option to their tempest configuration, they had to add it directly in the `defaults.yml`. This change proposes another approach, like we have for tobiko configuration: a default set of configuration entries, and a parameter allowing to override it. In order to avoid breaking existing configurations, the default value is still consuming the various parameters introduced over time - meaning most of the existing jobs shouldn't be affected.
cjeanner
force-pushed
the
test_operator/config-override
branch
from
bb725c3
to
f4f92b3
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/680a59fdab5242d596ac35c5a6df3f06 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 39m 46s |
|
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
This PR is stale because it has been for over 15 days with no activity. |
Until now, whenever someone wanted to add a new option to their tempest
configuration, they had to add it directly in the
defaults.yml.This change proposes another approach, like we have for tobiko
configuration: a default set of configuration entries, and a parameter
allowing to override it.
In order to avoid breaking existing configurations, the default value is
still consuming the various parameters introduced over time - meaning
most of the existing jobs shouldn't be affected.