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 >.
Natti Katz suggested an idea (#5491) · Sep 05, 2021 at 11:01 AM · cloudshellscriptsapi
This is a feature that is already present with shells. Shells can define their associated metadata via drivermetadata.xml
When distributing a resource script or blueprint level script it is a pain point for the admins that handle the upload to populate all this stuff manually in the GUI. Many times the admin doing the upload is not the same person that wrote the script. This upload misconfiguration leads to bugs. This places extra work on the developer to document all this metadata, and for the sys admin to properly add this manually.
The mechanism to define these fields should be in attached metadata files packaged with the scripts, similar to shells. This would also allow each script to be updated via api with its respective python version (currently will be uploaded as systems configured default python). An alternative is to add more parameters to the upload script api to set all this stuff (but I think a distributable package with metadata is cleaner, and just upload that via api without need for extra parameters)
The required data for scripts:
- script name
- script version
- python version
- visibility
- description
- attached models (for resource scripts only)
- categories
- alias
- parameters (and all the associated parameter metadata)
Thanks,
Natti
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.
create an API to copy the output console content
Need a CloudShell Sandbox API call that will return the tile image file of a given blueprint
support "admin only" Blueprint commands
Script parameters enhancements
API call to open (raise) the output window in the Web Portal
API call to get "Estimated setup duration" value from a Blueprint's Properties