action-managed-update=false set in bundle does not apply the configuration during initial deployment

canonical / charm-advanced-routing

This subordinate charm allows for the configuration of policy routing rules on the deployed host, as well as routes to configured services.

0 stars 3 forks source link

action-managed-update=false set in bundle does not apply the configuration during initial deployment #14

Open jneo8 opened 9 months ago

jneo8 commented 9 months ago

On a clean deploy, the advanced-routing charm doesn't honor the setting action-managed-update = false. Either config-changed or run-action apply-changes must be run on the units to affect the initial configurations in a bundle.yaml.

This is needed for Solutions QA and Foundation Cloud Engine automation.

Imported from Launchpad using lp2gh.

date created: 2020-09-15T17:05:29Z
owner: jhillman
assignee: None
the launchpad url

jneo8 commented 9 months ago

(by addyess) there is a config option that provides this feature:

juju config advanced-routing action-managed-update=false

jneo8 commented 9 months ago

(by afreiberger) addyess

We found today that deploying the charm in a bundle with action-managed-update=false does not auto-apply the settiings at charm install. You must follow-up with a config-changed or run-action to get the automatic change to apply to newly deployed hosts.

running the juju config will do the right thing, but not when deployed with that config from the bundle.