List of feature requests Sandbox Config management

Thanks @amie11 for the feedback. This is really helpful.

A list of the history of the environment will come in a few weeks with release 2. It will only show the explicitly saved “snapshots” so not all changes in an environment, but hopefully this goes some way to helping to see how things have progressed over time.

Export has come up a number of times and I've logged it internally as something for us to consider. Do you think you would also want to be able to import an exported configuration and have that “deployed” to an environment? 

Good point about the first message. I'll ask the team what we can do to make that clearer for customers.

hey @carl14 

You're most welcome. Some updates below for you. 

History : would it show in the existing audit log when someone has initiated a snapshot?  Snapshots are cool, but i'm more thinking… if there are multiple admins on the account for auditing purposes, it would be good to be able to see somewhere who initiated the snapshot and who saved it. If that will show in the existing audit log, then awesome. Otherwise I think its a worthy ad, other Admin 1, won't know if Admin 2 iniated a snapshot and at what time etc. 

Exports: The ability to export and import would be fab. Context: Some admins on the account may not be super technical i.e API minded and their dev resources live outside of ZD or could be a 3rd party. So they could export a snapshot config, provide the file to the dev, the dev can do whatever they want and then give it back to the admin to import back into the account. 

Side note: Imports & Exports would be amazing for ZD partners to utilise to push in pre-built config. 

This is super helpful. Thank you. 

This is what we're working on with regards to showing what versions/snapshots have been made. I'll chat with the team about including the user who made the snapshot too and see what we can do around that.

That looks like a nice layout there in the screenshot. 

Q: Can an admin save a snapshot, and then edit it and save it again as an update to that snapshot? 

If yes… i'd recommend adding in an “updated” column, which reflected the date/time of the most recent update to the snapshot. - Off the back of that it's also going to need to be recorded somewhere, whether inside this section or in the account audit logs, the name of the admin who made the update + date/time etc. 

Q: Can an admin save a snapshot, and then edit it and save it again as an update to that snapshot? 

If an admin changes some config in an environment, they can create a new snapshot/version to capture that change. You can't actually edit a saved version so no need for an updated timestamp I'd say.