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.
Michael Nassie suggested an idea (#1749) · Jul 18, 2017 at 08:51 AM · apisandboxsandbox apiuser permissions
would like to know what is the username of whoever is running a specific command, for every command run
currently, there is only deatils of a static admin user, or the sandbox owner.
this is not enough when multiple permitted users are running commands on the same sandbox
Meni Beso commented · Jul 19, 2017 at 08:34 AM
Hi Michael,
Thank you for submitting the idea,
Can you add more information about the exact use case, why do you need to know this? I mean is it an admin trying to debug a command? several users working on the same sandbox and trying to understand who did what?
Thanks
Daniel Delarosa commented · Nov 07, 2017 at 05:48 PM
hi Meni
In our case, the main reason is to make sure that a user is really running commands and using the reservation appropriately. Main reason we are using cloudshell is to make efficient use of the resources. So if a user reservation starts and no action is performed, we want to end the reservation. So for that we need logs, to make sure that the user is really using the resources. Also the use case of several users suing the same sandbox is applicable, since we want to know who is doing what.
Thanks
Meni Beso commented · Nov 19, 2017 at 10:54 AM
Thanks, I understand the use case now, I changed the idea to 'Considering' - we will consider implementing it based on its effort and priority.
Alona Getzler commented · Sep 12, 2018 at 08:00 AM
Hi,
I am happy to update that this idea is partially implemented in CloudShell 9.0, which was released about a week ago.
In 9.0 there is a new context available in orchestration scripts (a.k.a "blueprint commands") called reservationLifecycleDetails and it includes the username of the user which actually launched the command. Note that this context is not available in resource driers or scripts.
Alona.
Steven Geller commented · Dec 03, 2018 at 10:35 AM
Hi Michael,
This is done using reservationContextDetails. We have a section about this class in the dev guide's Getting the user context article.
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.
Sandbox API to return resource Address
Adding DELETE method to Sandboxes by ID
have a place to store information on the sandbox itself
Method to configure email notification for a sandbox
API call to get "Estimated setup duration" value from a Blueprint's Properties
Active with error sandboxes still return sandbox ID to Jenkins
add sandbox context component to any blueprint script