provide facility to deprecate config keys

Bug #1833094 reported by Peter Jose De Sousa
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

Hi,

With reference to https://github.com/juju-solutions/layer-docker/pull/137, when config keys have already been established, there is no way to provide a migration path between charm versions.

It would be nice to be able to `alias` between config keys of newer and older versions of charms.

E.G.

`charm changed config_key to config-key`

... config.yml
...
aliases:
  - - config_key:
        to: config-key.
...

Revision history for this message
Richard Harding (rharding) wrote :

I thought we had something around this in the bugs history but my search-fu fails me.

Thanks for the bug report. Definitely something that's come up a couple of times.

Changed in juju:
status: New → Incomplete
status: Incomplete → Triaged
importance: Undecided → Wishlist
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Wishlist → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.