Add metadata file to link to CLI deploy #170
Conversation
| @@ -0,0 +1,11 @@ | |||
| # DO NOT MODIFY THIS AUTO-GENERATED FILE. | |||
| # MODIFYING THIS FILE MAY CAUSE YOUR STACK TO NOT FUNCTION PROPERLY | |||
There was a problem hiding this comment.
Should we really claim this here?
There was a problem hiding this comment.
It is true, in the future we will use this UUID for other things too, so want to make sure no one modifies it
| @@ -0,0 +1,11 @@ | |||
| # DO NOT MODIFY THIS AUTO-GENERATED FILE. | |||
| # MODIFYING THIS FILE MAY CAUSE YOUR STACK TO NOT FUNCTION PROPERLY | |||
| uuid: "{{ uuid }}" | |||
There was a problem hiding this comment.
Idea: We could emit all these details as usage logs during template creation. Then we'll only have to persist:
uuid: <>
source_template: mlops-stacks
We could join on uuid during analysis.
There was a problem hiding this comment.
Would that be possible since bundle init doesn't require authentication right? Would we use the unauthenticated usage log endpoint for this? Also, we'd need to still attach UUID to that initial log during template creation
There was a problem hiding this comment.
Does mlops-stacks use the {{workspace_host}} helper? If so auth is required. It might be required even if you don't use the helper. I'd have to check.
There was a problem hiding this comment.
We don't use the helper (we ask the user to specifically input workspaces that they plan to deploy to)
No description provided.