Use cifmw_architecture_scenario file in set va scenario

openstack-k8s-operators/architecture#383 drops defaults.yaml scenario file in favor of openstack-k8s-operators/architecture#375. openstack-k8s-operators#2267 suggests to use Use cifmw_architecture_scenario to set proper automation file. Whereever default.yaml is used, the job broke. This pr fixes the same using cifmw_architecture_scenario file. Signed-off-by: Chandan Kumar (raukadah) <[email protected]>
openshift-cherrypick-robot · Sep 12, 2024 · d8cf5b1 · d8cf5b1
1 parent 8cec1bb
commit d8cf5b1
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/roles/kustomize_deploy/molecule/flexible_loop/converge.yml b/roles/kustomize_deploy/molecule/flexible_loop/converge.yml
@@ -35,12 +35,14 @@
 
     - name: Load architecture automation
       vars:
+        cifmw_architecture_scenario: hci
         _automation: >-
           {{
             (ansible_user_dir,
              'src/github.com/openstack-k8s-operators',
              'architecture/automation/vars',
-             'default.yaml') | path_join
+             cifmw_architecture_scenario~'.yaml')
+             | path_join
           }}
         _file: "{{ lookup('file', _automation) | from_yaml }}"
       ansible.builtin.set_fact: