community Welcome to Quali's Community Forums!
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) > |
Quali's Idea Box!
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.
Quali's Community Integrations
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 >.
Ben Abrams suggested an idea (#4113) · Nov 06, 2018 at 10:41 PM · jenkinsplugincloudshell
Cloudshell Jenkins Plugin: credential entry
I want the Cloudshell Jenkins Plugin to take Cloudshell credential information as input. Specifically;
- username
- password
- domain
I want these inputs available in both Freestyle Jenkins jobs and Jenkins Pipeline scripts.
Usecase: A single Jenkins instance serving multiple Cloudshell domains. Each Domain should have its own Jenkins user. Therefore, the current functionality of a global configuration for user credentials in the Jenkins Plugin does not work for me.
@Yaniv.K
has a zip file with a version of the Jenkins plugin that we modified in-house for this purpose. That implementation is hacky and should be refactored to conform more closely to the original plugin's design.
5 comments
· Add your reply
Alona Getzler commented · Nov 14, 2018 at 08:14 AM
Hi @babrams, thank you for posting this idea!
This idea definitely makes sense and we will add it to our backlog.
I do have few questions though - why do you need a separate user for each domain? won't one "automation user" with access to all domains will suffice? in this case you will just select the domain on each job or script.
As votes help us prioritize between the different ideas, we will appreciate the votes of anyone who is interested in seeing this idea implemented in the product.
Alona.
Ben Abrams commented · Nov 15, 2018 at 12:04 AM
@Alona.G - "won't one "automation user" with access to all domains will suffice? in this case you will just select the domain on each job or script."
Actually, yes. I believe one user in multiple domains and domain being an input to startSandbox would satisfy my needs.
Kim Horanyi commented · Nov 15, 2018 at 09:50 PM
While the alternate solution is functional, I think it wouldn't be the same security, as we would not be able to appropriately restrict domain access. It seems like any user with that service account could make reservations in any domain. Not all of our users should be able to make reservations in all lab environments, some are NDA restricted environments.
Dan Michlin commented · Dec 12, 2018 at 09:42 AM
Hi, I'm happy to update that this idea is planned to be delivered in the next official release of our Jenkins plugin.
we will allow sending "Domain" attribute as part of a Freestyle or pipeline job to CloudShell. this will allow your automation user to consume sandboxes based on the required domain
Dan Michlin commented · Jun 02, 2019 at 02:26 PM
Hi, I'm happy to update that this idea is included in CloudShell Jenkins plugin 1.6.3
Welcome to Quali's Community Forums!
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) |
Welcome to Quali's Idea Box!
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.
Quali's Community Integrations
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.
Your Opinion Counts
Help us make things better. Share your great idea or vote for other people's.
Follow This Idea
Related Ideas
Set of quali components informations published on cloudshell portal
Jenkins Sandbox API Plugin: Support custom Sandbox name
Instruction panel width control request
Ability to 'pop' the vSphere Console for vSphere resources
Input parameters as radio button
Extend Python cloudshell_api to add/delete script to/from environment
API calls to manage resource location with the RM Folder Structure
Connectivity search filter at the chassis level
pecify default auto arrange feature for an environment in portal
