Open sfromm opened 11 years ago
Presently considering creating two tables to support the extra fields: options and playbook_options. The latter would serve as a join table between playbook and options. options would look like:
id | option | value
---+-----------+--------
1 | limits | hosta,hostb
2 | forks | 5
3 | tags | dns
4 | inventory | /path/to/inventory
This should probably also implement closer integration with alembic for automatic database upgrades.
Should also store the following information that can be provided on the CLI for a playbook: