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 >.
Kimo Saper suggested an idea (#4996) · Feb 04, 2020 at 07:21 PM · job schedulingcloudshell portalblueprint
I would like to be able to associate more than 1 viable Blueprint to a Job with in a Suite, and thus make it a User input at the time of the run. This would allow the Job to be more flexible & easier to navigate for the user.
Currently if you have 10 blueprints that the Suite/Job is able to run against, then you have to create 10 Suites to handle this. Or with this implemented, you'd have 1 Suite and be able to select the Blueprint you want it to run against. Likely we'd need to also push forward the Blueprint being used somewhere in the line result that get's published later, for clarity. And yes, you can edit the suite, but that takes an admin to do (and would likely require them to edit it back to the original again).
An additional option with in this request might be to add all blueprints based on Domain - this would be an easy way to also keep it updated (if it always showed all blueprints by domain)
This is just an option when designing the suite, but one I think could be very useful.
I can easily see an upcoming project that will likely have a blueprint for each of the customer's installation sites, over 100, so needing a Automation Suite that allows the user to select the which site to run their job against.
Edit: Forgot to add the pictures
Dan Michlin commented · Mar 10, 2020 at 11:14 AM
Hi @Kimo Saper, thanks for the suggestion, while i do see the value of selecting differnt bluepritns per jobs , it's currently not in our roadmap
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.
Help us make things better. Share your great idea or vote for other people's.
Make Blueprint ID Visible in Catalogue 'More Info'
Execution log of a running CloudShell automation suite
CloudShell - UI changes for Blueprint Input
CloudShell - Give user ability to duplicate blueprints from one domain to another
ability to add blueprints to domains from cloudshell portal
Allow User Inputs for Jobs to have the same options as Blueprint Inputs (Job Scheduling)
Cloudshell Portal should consider Teardown time as time remaining instead of end time
Lock a Blueprint to prevent incidental changes
Resource has the Ability to display an attribute of the designer's choice on the canvas
Job Scheduling - Input improvement - Different Selection options.