Welcome to the Scratch Org Snapshots Open Beta!
We're thrilled to share a significant milestone in our journey together! Following the success of our Closed Beta, we're excited to announce that Scratch Org Snapshots is now entering the Open Beta phase with the release of Spring '24. Your continued support and invaluable feedback during the Pilot and Closed Beta have been instrumental in shaping this feature. We're grateful for your trust and dedication, and we're eager to take the next step with you.
Open Beta Highlights:
- Expanded Support: Performance Edition Dev Hubs can now access the Scratch Org Snapshot feature
- User Opt-In: Now, all production Dev Hubs can actively opt into the Scratch Org Snapshots feature without requiring a nomination process.
- Additional back-end changes to scale the service
For more information, please check out the Spring ’24 Release Notes and Help Guide.
How to Participate in Open Beta:
All customers can opt into using the feature by enabling the Snapshots setting with the Setup menu of their Dev Hub. Instructions for enabling the feature are available here. Customers who were a part of the Closed Beta will need to enable the setting to continue accessing the feature, however, they will be able to use their existing active Snapshots.
What's Next on the Roadmap:
As we progress towards our goal of making Scratch Org Snapshots generally available by Summer '24, we're committed to continuous improvement. Here is a sneak-peek into the upcoming changes in Summer ’24 (safe harbor applies):
- Support for Salesforce Platform and Salesforce DX Limited Access license
- Increasing Snapshot expiration from 30 to 90 days
- Auto-cleanup of expired Snapshots
- High priority bug fixes
We Value Your Feedback:
Your feedback has been pivotal in our journey so far, and we encourage you to keep sharing your insights. The collaborative spirit of this community is what makes Scratch Org Snapshots great, and we're eager to hear your experiences during the Open Beta.
Thank you for being a crucial part of this exciting endeavor. Together, let's continue shaping the future of Scratch Org Snapshots!
@Matt Lacey, 100%. Automatically expiring snapshots are useless to me, especially in scenarios where work on extension packages may be quite intermittent. A limit of 5 active ones is also way too low.
I commented on a previous thread, going into the way I would like to use these snapshots, and why that means long-lived snapshots are what we need. Without this, we are pretty much back to "scratch org pooling", where we have automation like dx@scale has to simply create scratch orgs that we may need so that the dev or CI pipeline doesn't have to wait while the org is built...
I would be happy to have an automated "pool size", so if I require a different snapshot setup and already have used all my snapshots up the least recently used snapshot is dropped and a new one created at that point.
This latter works if the setup and identification/selection of snapshots is essentially transparent, based on the set of CLI commands used to build it (with a specific "this is where the snapshot setup finishes" command the only addition required in the script that orchestrates the setup).
