Projects should support variables, which other entities use in resolution
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
craton |
Fix Released
|
Critical
|
Thomas Maddox |
Bug Description
This will enable support for project-wide variable setting, where this makes sense. Examples:
project -> region -> cell? -> device|network, including network_device
-> network_interface
-> worflow def -> workflow
-> user
Note that network_interface has variables, but it does not really fit into the resolution tree approach, given that it's used to form graphs. But starting with project makes sense for it.
Acceptance Criteria:
1. Support for GET, PUT, DELETE on /v1/projects/
2. Variables also included in the response for GET /v1/projects/
3. Variables also included in the response for POST on /v1/projects
4. Variables set at the project level must resolve for all lower-level resources belonging to a particular project.
5. CLI support for aforementioned endpoints following the same UX as Cells, Regions, Hosts, etc.
Changed in craton: | |
assignee: | nobody → Thomas Maddox (thomas-maddox) |
Changed in craton: | |
status: | New → In Progress |
description: | updated |
Changed in craton: | |
importance: | Wishlist → Critical |
Changed in craton: | |
milestone: | none → v0.1.0 |
Have any of the parties that have contributed use cases actually cited this as something they want and/or need?