V4_CFG_CLUSTER_NODE_POOL_MODE set to minimal - does not update

[ninewb]

Viya4 Deployment Version Details

2024.04, Stable

viya4-deployment local repo was updated on May 22.

Ansible Variable File Details

V4_CFG_CLUSTER_NODE_POOL_MODE: minimal

Steps to Reproduce

• ansible-vars.yaml file updated with config param
• reran deployment expecting the transformers to be udpated based on param

  docker run --rm \
    --group-add root \
    --user $(id -u):$(id -g) \
    --volume $(Agent.BuildDirectory)/viya4-deployment/deployments/$(KIND):/data \
    --volume $(Agent.BuildDirectory)/viya4-deployment/assets:/assets \
    --volume ${ASSETS}/$(GUID)-aks-kubeconfig.conf:/config/kubeconfig \
    --volume ${BUILD_DIR}/ansible-vars.yaml:/config/config \
    --volume ${ASSETS}/terraform.tfstate:/config/tfstate \
    --volume ~/.ssh/id_rsa:/config/jump_svr_private_key \
    $(kv_acr)/sas-viya4-deployment:latest --tags "baseline,viya,cluster-monitoring,viya-monitoring,install" -vvv

• do not see a change

Expected Behavior

kustomization.yaml being updated and overlays having the two additional transformers.

Actual Behavior

deployment succeeds without changes.

Additional Context

I see the sizing.yaml gets included but no other verbosity beyond this. I am not sure if i have false expectations of what should occur here or using the config param incorrectly. I wanted to test out overlays/scaling/single-replica/transformer.yaml without scripting the processing since I presume it should be done with V4_CFG_CLUSTER_NODE_POOL_MODE: minimal.

TASK [vdm : Include Sizing] ****************************************************
task path: /viya4-deployment/roles/vdm/tasks/main.yaml:186
included: /viya4-deployment/roles/vdm/tasks/sizing.yaml for localhost
Monday 17 June 2024  17:41:57 +0000 (0:00:00.077)       0:04:14.855 *********** 
Monday 17 June 2024  17:41:57 +0000 (0:00:00.028)       0:04:14.884 *********** 

References

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct