Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
conjure-up continue operations #624
Comments
battlemidget
changed the title from
conjure-up against existing deploys expose actions
to
conjure-up against existing deploys to perform "next steps"
Jan 26, 2017
|
We can utilize the model-config api for storing a string of yaml/json metadata within an 'extra-info' key in order to give us the ability to perform different tasks based on what data is available for conjure-up. |
|
I'd like to add a reminder here that once this is done, the conjure-down destroy controller should only show you models that have the extra-info key - so you can only conjure-down models that were conjured-up. |
battlemidget
modified the milestone:
later
Jan 30, 2017
mc0e
commented
Jan 31, 2017
|
See also #641 (comment) |
battlemidget
modified the milestones:
2.1.1,
later
Jan 31, 2017
battlemidget
modified the milestones:
2.1.1,
2.2.0
Mar 1, 2017
battlemidget
modified the milestones:
2.2.0,
2.2.1
Mar 17, 2017
battlemidget
referenced this issue
Mar 22, 2017
Closed
allow user to select a model on a controller to deploy to #753
battlemidget
modified the milestones:
2.2.1,
later
Apr 1, 2017
battlemidget
changed the title from
conjure-up against existing deploys to perform "next steps"
to
conjure-up continue operations
May 4, 2017
|
This should also include providing the ability to run additional actions against an existing deploy. |
battlemidget
modified the milestones:
2.2.1,
later
May 4, 2017
battlemidget
modified the milestones:
2.2.1,
2.3.0
May 25, 2017
battlemidget
added
the
critical
label
May 25, 2017
battlemidget
closed this
May 25, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
battlemidget commentedJan 25, 2017
For things like kubernetes we could re-run conjure-up against it and present the user with a list of actions to perform against the cluster.