chore: match environment CS config.yaml variable to the ARO-HCP env name#4055
Conversation
9bd5945 to
aa41927
Compare
aa41927 to
4a7d500
Compare
|
/lgtm |
4a7d500 to
99acb3e
Compare
99acb3e to
6f9038f
Compare
|
/lgtm |
6f9038f to
8aa7ad6
Compare
|
/lgtm |
8aa7ad6 to
a814b7e
Compare
|
/lgtm |
|
/retest |
|
/lgtm |
|
/retest |
1 similar comment
|
/retest |
|
/lgtm |
|
/retest |
4 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/retest |
dda1dc8 to
0cf0aa6
Compare
|
/lgtm |
|
/retest |
1 similar comment
|
/retest |
|
/lgtm |
|
The failure in https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/Azure_ARO-HCP/4055/pull-ci-Azure-ARO-HCP-main-e2e-parallel/2025936945640640512 is because the e2e verifier in https://github.com/Azure/ARO-HCP/blob/main/test/util/verifiers/kusto.go#L170 assumes that the NamespacePrefix is |
The environment config.yaml variable used by CS had the value of arohcpdev for all dev env based envs. We change it to use the aro-hcp environment key value. The format being arohcp<envname>. This variable value is used by CS to: - Define the Maestro Source ID - As a base for some K8s Names and Namespaces in the Management Cluster In that way we match the ARO-HCP environment name. Changing it has an impact on the ability to see previously existing Maestro resources but the change is performed only on dev envs which are ephemeral. The exception is the shared dev env but in that case no changes occur.
0cf0aa6 to
463a6d0
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: geoberle, machi1990, miguelsorianod, raelga The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
1 similar comment
|
/retest |
The environment config.yaml variable used by CS had the value of arohcpdev for all dev env based envs. We change it to use the aro-hcp environment key value. The format being arohcp. This variable value is used by CS to:
In that way we match the ARO-HCP environment name.
Changing it has an impact on the ability to see previously existing Maestro resources but the change is performed only on dev envs which are ephemeral. The exception is the shared dev env but in that case Used by CS to define the maestro s