Set default Blueprint when starting a Sandbox from scratch #143
Quali-Community
started this conversation in
Useful Tips & Guides
Replies: 1 comment
-
Hi, In the past few CloudShell versions we started hiding the option to create an "empty sandbox" by default. As we see it the flow should always start from a blueprint that gets reserved. You can create a baseline blueprint with the basic orchestration and use this blueprint as a starting point for these ad-hoc sandboxes. Note that you can also create blueprint templates to be selected when users create new blueprints. By the way, such requests or feature related ideas should be placed in the Ideas section of the community in the Forums section. Alona. Alona Getzler (Alona.G) - 03/26/2018 07:19 AM
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have a number of users (including myself), that create Sandbox reservations on the fly.
We would like Cloudshell to load a "default" Blueprint for the Sandbox if the user doesn't select one.
This will allow the correct command drivers to be for all sandboxes.
The work around is to save the Sandbox to a Blueprint, select the correct drivers, and restart the Sandbox.
Jim Wharton (jim.wharton) - 03/23/2018 07:53 PM
· 3464 ·
Beta Was this translation helpful? Give feedback.
All reactions