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.
Kimo Saper suggested an idea (#5001) · Feb 10, 2020 at 10:29 PM · inputsblueprintshelladministration
Ideally, Blueprint Inputs could inherit from Object within the Blueprint automatically. Say you have a service that wants the User's Login info (vs a global or service account for auditing purposes), the Shell design would have a section that designates items to be added to the Blueprint's inputs.
This would simplify blueprint design, in that anytime objects that are looking for/dependent upon blueprint inputs are automatically added. In addition during a sandbox, should an item with these requirements be added, a dialog box would appear asking the user to input them at that time (and updating the sandbox's inputs/values)
The other advantage of this should the needed parameters or defaults change, then only the shell needs to be updated, vs, potentially 100's of blueprints.
Kimo Saper commented · Feb 10, 2020 at 10:32 PM
The other area I see this being really useful is for Cloud App deployment, again, being able to traceback the user launching the app based on the Account Login for bill back - that way AWS/Azure etc has a specific record of the user that launched the app - vs trying to go back thru just Reservation information to formulate billing.
Dan Michlin commented · Mar 10, 2020 at 11:20 AM
Hi @Kimo Saper, thank you for the interesting suggestion, we will look into the various use case and consider it
Extend your CloudShell capabilities by creating your own Shells. Share your knowledge with the world and be part of our growing community
Help us make things better. Share your great idea or vote for other people's.
Auto Show Instructions per Blueprint
Add the ability to flag Shell Attributes for Abstract from Web Portal
Gen2 Service Shells need to be able to managed by Categories
Save sandbox as blueprint - include updated global inputs
Display set attribute pull down list of Global input(Lookup) by alphabetical order
API for editing blueprints without re-packing them
Option for CloudShell to Kill and Rebuild Shell venvs