Add a --yolo flag for 'juju config'

Bug #1827287 reported by James Troup
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

Changing the config value for some charms (e.g. 'l2-population' for neutron-api charm) can have significant impact to the workload of that charm (in the example case VM network traffic is disrupted temporarily). It would be nice if Juju had some way for charm authors to specify that a config option is dangerous to change and some way for charm users to specify that they accept the danger (e.g. --yolo).

Revision history for this message
James Hebden (ec0) wrote :

An example, where a flag is added to the config.yaml for the setting to indicate it's a risky move to change it:

  l2-population:
    type: boolean
    yolo: true
    default: True
    description: |
      Populate the forwarding tables of virtual switches (LinuxBridge or OVS),
      to decrease broadcast traffics inside the physical networks fabric while
      using overlays networks (VXLan, GRE).

Attempting to change it should yield a message and refuse the change:
juju config neutron-api l2-population=true

Desire state, results in:
ERROR: Changing 'l2-population' to 'true' is marked as dangerous by charm 'neutron-api'. Please consult the charm documentation to understand the risk, and indicate that You Only Live Once by adding the --yolo flag if you wish to proceed.

Adding the hypothetical --yolo flag:
juju config --yolo neutron-api l2-population=true

The desired outcome is that the change is made as normal when the flag is passed.

Tim Penhey (thumper)
Changed in juju:
status: New → 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.