Now we have some use cases about set/unset properties,
try to redefine devref to find out a best and easiest
solution to keep commands simple and clearly.
Five use cases exist in property action, "append",
"update", "remove", "clean", "override", the following
rules can cover all these use cases:
1. append ==> "set --property new-key=value"
2. update ==> "set --property existed-key=new-value"
3. remove ==> "unset --property existed-key"
4. clean ==> "set --no-property"
5. clean ==> "unset --all-property"
6. override ==> "set --no-property --property new-key=value"
Related blueprint support-no-property-in-aggregate and
blueprint allow-overwrite-set-options.
Change-Id: If86daf6989d8e0ad0dc6e590d7636be7d5203a18
Some options are required in some commands, I think we need
a document to state what should we do in this case.
Change-Id: Id345ca1790e2125b333b271b74288e1a73d39ba3
Update the devref to add the describe and code example about
overwrite options behavior.
Change-Id: I65e9a3a30acf8d427906096bde24fa8b4c3ac3f7
Implements: blueprint allow-overwrite-set-options
Add a developer reference for options with choices. This patch set
also includes RST doc formatting fixes.
Change-Id: I5fd6a699806edf1d2d95110f0b8a2b8a385028ab
Modify 'code-block' tag format so that the following python code
could be showed exactly, and reformat the more than 79 chars of lines.
Change-Id: Ic6721e4cc8f4c7a3e4a7c7dbd63d9089180cdc33
Add a developer guideline for command options to define the options
used across multiple commands and make them behave consistently.
Change-Id: I1dbbafe8061e10b271cd55cac056731508c52204
