Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Application.refresh() does not support passing new config options #981

Open
aieri opened this issue Oct 26, 2023 · 0 comments
Open

Application.refresh() does not support passing new config options #981

aieri opened this issue Oct 26, 2023 · 0 comments
Labels
wishlisted requested feature

Comments

@aieri
Copy link
Contributor

aieri commented Oct 26, 2023

Description

When using the juju CLI I can perform a charm refresh and config change in a single command. From the docs:

Charm settings may be added or updated at upgrade time by specifying the
--config option, pointing to a YAML-encoded application config file.

  juju refresh foo --config config.yaml

This is useful and sometimes even necessary (e.g. if the revision we are upgrading to has a new config option whose default we explicitly need to avoid using), but libjuju does not currently allow for the same behavior.
See

'config_settings': None,

Urgency

It would save from a weird workaround

Code I'd Like to Run

await app.upgrade_charm(
    channel=channel,
    force_series=force_series,
    force_units=force_units,
    path=path,
    revision=revision,
    switch=switch,
    config=new_config_dict,
)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wishlisted requested feature
Projects
None yet
Development

No branches or pull requests

1 participant