[2.0] operations not correctly documented?
Bug #1566115 reported by
Andres Rodriguez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Expired
|
Critical
|
Unassigned | ||
| 2.0 |
Expired
|
Critical
|
Unassigned | ||
Bug Description
On the CLI is possible to do:
maas <user> file read <filename>
or
maas <user> files read
The first is nto docum,ented as an Operation o=n the API, where as the second one is:
File
Manage a FileStorage object.
[...]
GET /api/2.
GET a FileStorage object as a json object.
The ‘content’ of the file is base64-encoded.
[...]
Files
[...]
GET /api/2.0/files/ op=read
List the files from the file storage.
The returned files are ordered by file name and the content is excluded.
| Changed in maas: | |
| milestone: | none → 2.0.0 |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #1 |
| Changed in maas: | |
| status: | New → Incomplete |
| Changed in maas: | |
| importance: | Undecided → Critical |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
To post a comment you must log in.
This bug report is very confusing and overall miss typed like crazy. Its hard for me to even deduct what your trying to report.
I have looked at both the FileHandler and FilesHandler and all methods have a docstring. op= where cleaned very recently so make sure this is the latest trunk, before updating this bug report.