Scope attribute not shown in List, Get operations
Bug #1746681 reported by
Jose Castro Leon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-mistralclient |
New
|
Undecided
|
Theodoros Tsioutsias |
Bug Description
When using the CLI and creating workbooks and workflows, the scope can be specified to make them private or public. Once done this attribute is not shown up later, so you don't know if the resources you have created are public or not.
To make it even worse, if you want to update the workflow or workbook with a new definition you need to specify the scope and if you want to keep it as it is you don't have a way on the CLI to retrieve this information.
Changed in python-mistralclient: | |
assignee: | nobody → Theodoros Tsioutsias (ttsiouts) |
To post a comment you must log in.
The parameter scope is not handled by the workbooks API so we can ignore it for this bug