External-Mirrors/awx
2
0
Fork 0
mirror of https://github.com/ansible/awx.git synced 2026-01-10 15:32:07 -03:30
Code Issues Packages Projects Releases Wiki Activity

Update TODO notes.

Browse Source
This commit is contained in:
Michael DeHaan 2013-04-02 13:20:59 -04:00
parent 9307e2de26
commit dbab673183
1 changed files with 19 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
TODO.md
View File

@ -17,33 +17,37 @@ TODO items for ansible commander
REST TODO
---------
* project/teams
* credentials objects
* credentials objects & permissions
* tags
* audit trails
* launch jobs
* launch jobs triggering
* related resources on everything that makes sense
* expose log data from callback (decide on structure)
LATER
-----
* acom logging callback
* UI layer
* CLI client (and libs)
* UI layer, CLI client (and libs)
* clean up initial migrations
* init scripts, Apache proxying, etc
* does inventory script need any caching
* credentials subsystem -- let app hold on to keys for user
* init scripts (supervisord), Apache proxying, etc
* does inventory script need any caching (??)
* support multiple project launch options (different flags, etc)
TWEAKS/ASSORTED
---------------
* project should be able to define an inventory path and if NOT set it in launch job it could come from the project
* add a synthetic bit to the organization to indicate if the current user is an administator of it
* uniqueness checks for playbook paths?
* allow multiple playbook execution types per project, different --tag choices, different --limit choices (maybe just free form in the job for now?)
* permissions infrastructure about who can kick off what kind of jobs
* root API discovery resource at /api and /api/v1
* security check - playbook must be fully pathed when executed by commander and relative to project
directory. Project directories must be unique and be (also no ../, etc). default_playbook MUST be a relative path (no starting with . or / or containing ..).
* when creating a project, write a '.acom' file, this file contains a JSON list of valid project GUIDs that are allowed to use it. This can be created automatically by the system if it does not already exist, but not overwritten by the system.
* document multi-org content limitations with regard to access security and sensitive vars
* when app starts it creates a default organization and all superusers are automatically added to it
* API discovery resource at /api and /api/v1
* audit/test read only fields like creation_date
QUESTIONS
---------
* if creating a project, do we want to have an appliance style path for them, like
/storage/projects/GUID ??? may want to keep somewhere else ?