WIP: API specification for Column REST service #20
Conversation
|
@kars7e, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
| options: | ||
| type: "object" | ||
| $ref: '#/definitions/Options' | ||
| extra_vars: |
There was a problem hiding this comment.
why is extra_vars out of 'options' ?
| - http | ||
| basePath: /v1 | ||
| paths: | ||
| /tasks: |
There was a problem hiding this comment.
I think "tasks" might be confused with Ansible tasks in a playbook. Rather some other noun not already used such as "job", "run", etc
There was a problem hiding this comment.
yes, 'run' would be better.
I will pushed a scratch patch by using flask api.
| info: | ||
| description: Column - Ansible as a service | ||
| title: Column | ||
| version: 0.0.1 |
There was a problem hiding this comment.
Is this supposed to be a separate version from column version?
| type: array | ||
| skip_tags: | ||
| type: array | ||
| susbset: |
| get: | ||
| summary: "Retrieve Task by its ID" | ||
| description: "Returns single task given its ID" | ||
| operationID: "getTaskByID" |
There was a problem hiding this comment.
some parameters are using camelcase others using underscore (playbook_path)
This WIP for API specification for column REST service. all comments & feedback welcome!
This change is