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 >.
I use PyCharm to edit orchestration scripts and with help of plugin upload them to the Quali server.
Currently, I have to use Quali web interface (Portal > Manage > Scripts) to edit the version info after the script is uploaded.
Is there any file (in my script project) to update version info of the script?
----
For the resources and the services, it seems the right place is .\src\drivermetadata.xml. The content of .\version.txt is ignored, as far as I can tell.
Answer by Yaniv Kalsky · Jan 19, 2018 at 06:29 PM
There are few places to set the version (depends on the type of driver/script/gen):
1. For 1st gen drivers, as you noted, the location to set the driver version would be in the src\drivermetadata.xml file.
2. For 2nd gen shells, you don't see the driver on its own in the UI, so the shell version is the value that you'd like to maintain. You can do that by updating the shell-definition.yaml. You can also update the driver version in the drivermetadata.xml file, but this value will not be exposed anywhere.
3. For scripts it's currently more problematic. The only way to update the version "automatically" is by uploading the script as part of a package, where the datamodel.xml has the version number. You can have a template folder of such a package, where you update the script/s files and update the datamodel.xml, and then zip and upload that package.
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.
Saving details from setup for use in teardown 3 Answers
How to implement timeout? 1 Answer