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.
Natti Katz suggested an idea (#4876) · Nov 24, 2019 at 02:03 PM · pythonofflineorchestrationpackageautomation
So currently the behavior is to look locally first, and if an identical package name is found yet an incorrect version, there will be no call to online pypi.
For example. I place requests 2.18 in my local pypi. I run a script that asks for requests 2.22. Local pypi will be searched, finding requests package, but then tells me it's the wrong version and will not look online. Yet if I have no requests package it will look online for it.
I believe this is inflexible, because now as I soon as I decide to place a single offline package, I am hard commiting to providing all versions of that package offline. This can also unknowingly break orchestration for other users in the same system that were depending on the online lookup.
Muli Wienrib commented · Nov 26, 2019 at 08:32 AM
Hi Natti,
Thank you for the suggestions, unfortunately, this is the PyPi behavior as designed.
One of the motivations for this is limiting the supported versions of a package in the local PyPi for a site
Cheers
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.
add sandbox context component to any blueprint script
concurrent environment command support for setup
The CloudShell orchestration package needs to be in the script Python env by default
Ability to Connect/Disconnect All Routes by device
Quali Python API, Resource Attributes Values converted to match listed type
Support version.txt file in a script package
API call for moving a blueprint to another folder
App Installation to be able to download dependencies from repository (support for requirements.txt)
Limit the amount of times shells/scripts requirements are being updated