977b16b2cc
This change partially implements pulumi/coconut#94, by adding the ability to name targets during creation and reuse those names during deletion and update. This simplifies the management of deployment records, checkpoints, and snapshots. I've opted to call these things "husks" (perhaps going overboard with joy after our recent renaming). The basic idea is that for any executable Nut that will be deployed, you have a nutpack/ directory whose layout looks roughly as follows: nutpack/ bin/ Nutpack.json ... any other compiled artifacts ... husks/ ... one snapshot per husk ... For example, if we had a stage and prod husk, we would have: nutpack/ bin/... husks/ prod.json stage.json In the prod.json and stage.json files, we'd have the most recent deployment record for that environment. These would presumably get checked in and versioned along with the overall Nut, so that we can use Git history for rollbacks, etc. The create, update, and delete commands look in the right place for these files automatically, so you don't need to manually supply them. |
||
|---|---|---|
| .. | ||
| basic | ||
| conversions | ||
| scenarios | ||