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 >.
Leeor Vardi suggested an idea (#4268) · Jan 02, 2019 at 12:43 PM · orchestrationcloudshellcloudshell portalportal
Currently, when looking at the commands pane of a resource, there is no way to know if a command is a resource command, or a connected resource command.
This is a problem because when a Blueprint Designer wants to customize the orchestration of a blueprint, it is very likely that he will try to execute the command via "ExecuteCommand" API (instead of the correct ExecuteResourceConnectedCommand) and will run into errors.
Suggested change: Make some visual indicator available in the portal that will identify the command as a Connected Command, with a tooltip that would indicate which resource the command belongs to.
Mock up of how it would look (maybe different icon?)
Ariel Benary commented · Jan 02, 2019 at 02:56 PM
Hi,
Thanks for submitting this idea.
I believe that for most sandbox users, the distinction between resource and connected commands is not important, and there is an advantage in seeing it all without distinction.
I believe the solution should be in the API- either have a new API that returns both resource and connected commands, or add type information to the existing GetResourceCommands API
Ariel
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 Resource Descriptions visible in CloudShell
CloudShell - Give user ability to duplicate blueprints from one domain to another
Option for CloudShell to Kill and Rebuild Shell venvs
API call to open (raise) the output window in the Web Portal
add the version/patch ID to the build number in the Cloudshell portal help
Set Root Resource Folder for a Domain
Set of quali components informations published on cloudshell portal
Email notification for all users or a group of users when Setting up a future maintenance window