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.
I am trying to stop & terminate command on a Service, and getting this warning:
One instance of a Service cannot be shared across multiple sandboxes, right?
I should be able to stop/terminate it without impact on any other (currently running) command of the same Service type.
***
Similarly, if a Resource is used exclusively in one sandbox, terminating command on the resource driver of that resource should not impact other command executions using the same driver (code).
It is confusion that the 'driver' is used for both, code/package and the instance of driver in the memory
The driver command executions (instances) are sharing the same driver code. It is not clear if there is any impact on other command executions if one of the (driver) instances gets stopped or terminated.
Answer by Yaniv Kalsky · Aug 13, 2019 at 02:55 PM
Yes, each service, even from the same type, will have its own driver instance - so terminating one will not affect the other instances.
For resources, it works in a similar way, but each resource will have its own driver instance. The warning is about resources that in some cases can be shared between multiple sandboxes, and in such cases when you terminate the driver in one sandbox it can affect other users/sandboxes. This will also not affect any other resource that uses the same kind of driver, as it will terminate the specific instance of this driver.
In your case, you say that the resource is exclusive to the sandbox, so no one else will be affected by this.
Ideally, this message will appear in very specific scenarios: when a resource is shared (and in use in another sandbox) or when other commands are running on that resource/service (as they can support concurrent executions). But it's good to be aware of it anyway.
Anyway, we can ask to make this message more clear/specify that it's the driver instance that is going to be reset and not the 'driver'.
And, the Terminate is only available for Admins, a user can only stop a command he executed, but cannot terminate it or the driver.
Answer by George Rainovic · Aug 13, 2019 at 03:02 PM
Hi Yaniv, Steven,
Thank you for providing the answers.
Answer by Steven Geller · Aug 14, 2019 at 10:54 AM
Hi George,
Thanks for bringing this up. We'll clarify these points in the documentation.
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.