[Feature]: Detail pages should include link to yaml used to create object

[colinjc]

Problem

If someone runs dstack apply without committing the config, there's no easy way to reproduce what they did. The UI doesn't always include all settings they used, and manually writing a yaml to reproduce is awkward.

Solution

Whenever running apply dstack should store a copy of the yaml and link to it from the instance page.

Workaround

No response

Would you like to help us implement this feature by sending a PR?

No

[r4victor]

@colinjc, not all runs are created from yaml configurations since runs can be submitted via Python API or HTTP API. Thus, dstack doesn't store the submitted yaml internally but a json representation of the configuration. We can convert this json to yaml back and show it in the UI / make it downloadable so that you can inspect the configuration and reproduce the run. Just note that it won't be syntactically the same as the submitted yaml configuration (e.g. it will have the defaults set). Still, it will be functionally equivalent to the submitted yaml configuration and should work for reproducibility purposes. Moreover, it should be better for reproducibility since defaults may change across versions, so you'd likely want to see the configuration with all parameters set. Please confirm if it works for you.

[colinjc]

Yep, key aspect is reproducibility so that approach makes sense to me

[peterschmidt85]

+1 to this issue, this would greatly help to troubleshoot runs

[colinjc]

Strongly recommend not printing env variables here, since that's the only supported path for getting secrets in atm