Thanks for spending the time with me yesterday. Here are some notes from our conversation:
Prompted Variables for Offline Drops
I think this is the closest suggestion we have so far for this kind of feature. I’d suggest lending your support and providing some specifics about your use-case and how you’d see it working. https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/12794610-allow-for-display-and-edit-of-offline-variables-at
I’ve emailed an invitation to comment on that working document.
Suggestion: Library Variable Set per Tenant
As I mentioned, I think you’ll have a better experience while you are still using Library Variable Sets, to use each set as a sandbox. There are some downsides (needing multiple sets, and scoping each variable manually) but you should get the isolation you’re hoping for.
Suggestion: Make each developer/tester a Tenant
A core tenet of Octopus is to make your deployments as consistent as possible across your environments. In this case I’d recommend modelling any of your “sandboxes” in the same was as you do for Production. When each developer/tester becomes a tenant, you’ll be exercising the self-same deployment strategy across all your environments. Plus you’ll have the dashboard telling you the truth about your sandboxes, and make it harder to pave over someone else’s sandbox. Plus you won’t have to use the “Include Specific Machines” workaround you showed me.
Can you take a backup of your SQL Server database for Octopus, zip it and upload it to the location in the email I’ve sent?
Hope that helps!