Feature request: Config tagged as mandatory
Bug #1941925 reported by
Erik Lönroth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
To have the ability to tag options with "mandatory" such that deployment is not allowed at all, unless explicitly provided would help developers as well as users to "do it right" before deploying and ending up in difficult to manage situations after deploy.
The deployment could be halted altogether somehow at this point, asking the users to provide options strictly needed to move on.
A bundle deploy could collect the union of all requirements before deploying aswell.
The developer could be helped alot from this by not having to write code to guard from trivial misconfigurations.
Revision history for this message
| james beedy (jamesbeedy) wrote | #1 |
Revision history for this message
| Erik Lönroth (erik-lonroth) wrote | #3 |
| Changed in juju: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| tags: | added: config |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #4 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
+1