Skip to content

Commit

Permalink
Use cifmw_architecture_scenario file in set va scenario
Browse files Browse the repository at this point in the history
openstack-k8s-operators/architecture#383 drops
defaults.yaml scenario file in favor of
openstack-k8s-operators/architecture#375.

#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) <raukadah@gmail.com>
  • Loading branch information
raukadah authored and openshift-merge-bot[bot] committed Sep 12, 2024
1 parent 8cec1bb commit db4b0d8
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion roles/kustomize_deploy/molecule/flexible_loop/converge.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down

0 comments on commit db4b0d8

Please sign in to comment.