These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
VISIT OUR DIFFERENT FORUMS:
Announcements > | |
CloudShell > | TestShell > |
Developers > | BI (Business Inteligence) > |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide > | Configuration Management > |
Getting started with Shells > | Extending CloudShell with Cloud Providers > |
Getting started with Orchestration > | API Guide > |
To share your integration, follow the instructions in this guide >.
When adding a resource to inventory using a shell, it gets put directly into Root on the Explorer tree. Is it possible to configure that so that resources can be better organized? Ideally it would be configurable per-instance, but at minimum can it be configured per-shell (e.g. in shellconfig.xml)?
Answer by Yaniv Kalsky · Sep 11, 2017 at 01:11 PM
This option is now available in CloudShell 8.1
Answer by Yaniv Kalsky · Feb 18, 2017 at 02:29 AM
To your question - no, it's not possible today.
Not sure if having it as a default in the shell level is good enough. Anyway since you can navigate the Inventory, the better option would be that the resource will be created in the folder you're currently in.
Anyway, you should probably open an Idea for that.
Yaniv
Answer by BeaconRed CSA · Aug 16, 2020 at 01:04 AM
this is an important requirement. With hundrends or thousands of blueprints the sandboxes should be organized in the same way.
Answer by Kimo Saper · Aug 20, 2020 at 05:35 AM
For @BeaconRed CSA
Blueprints can be assigned to folders in Resource Manager by domain, so they don't clog up that list. And if proper categories are created for blueprint organization, it's fairly easy to modify a blueprint's properties to put it in an available category. Categories can be associated with domains.
Answer by BeaconRed CSA · Nov 30, 2020 at 02:35 PM
Hi again, this requirement is related with the sandboxes being created inside VCenter for example.
By default all the Sandboxes and live machines are created in just one single folder depending on the configurations of the provider connector. It would be good to have a capability to have some organization inside the VMware or any other provider.
These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.
AlcatelTimetraRouterShell2G shell discover Error 7 Answers
Unable to select search attribute unless it's tagged as setting 6 Answers
Shell for Dell EMC Networking N-Series N1100-ON Series 1 Answer
Calient L1 Driver Version Support 3 Answers
Has anyone installed CloudShell into an OpenShift environment? 0 Answers