Tacker: The vnf-create --config-file and --config options should be mutually exclusive
Bug #1475785 reported by
Bob Haddleton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
Fix Released
|
Low
|
Bob Haddleton |
Bug Description
The tacker vnf-create command has --config-file and --config options which should be mutually exclusive. If the user specifies both a config file with --config-file and a specific configuration with --config, the text that is read in from the config file will be overwritten by the contents of the --config option.
Updating the add_parameter code to make these two options mutually exclusive will prevent this problem.
Changed in tacker: | |
assignee: | nobody → Bob Haddleton (bob-haddleton) |
status: | New → In Progress |
description: | updated |
tags: | added: tacker |
Changed in tacker: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Bob, Team:
I'm wondering why we need to support these two options ? Particularly for a CLI I think we should consider dropping --config.
The parameter value is limited shell max size. Beyond simple, small sample templates this might actually trip our users.
What do you think ?