Let the client tool use decide whether to call schema GET APIs and validate the schemas
Registered by
Maty Grosz
> Allow the user to decide, with an additional command option, whether the client tool will call the schema GET APIs and then validate the resposned schema. Once the option is included - the schemas validations (image or member) will be skipped.
> Suggested option name will be - "--noschema"
> This is significant in case of other applications that expose OpenStack APIs: These application may need less focus or won’t expose schema GET APIs at all, and thus the client tool will be able to skip the schema validations.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Looks like this needs to be filed under https:/
I'm a bit skeptical, however, of not validating with the schema.
markwash rejected 2014-02-18
(?)