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 >.
Natti Katz suggested an idea (#5311) · Jan 10, 2021 at 12:35 PM · configuration managementcloud providersexecution server
Current default behavior is for cloud provider selector to over-ride the selector value on the config management service.
This creates scenarios where the config can't be decoupled from deployment.
The best solution would not be to let the service override the cloud provider, rather let the Selector on the resource level override the cloud provider. (same expected behavior with normal shell commands)
Thanks,
Natti
Natti Katz commented · May 30, 2021 at 12:16 PM
To clarify:
The desired behavior is that the resource level selector attribute, if populated, will take precedence over the selector defined on the cloud provider resource that was used to deploy the app.
If the selector is empty, it can continue to fall back and be defined by the cloud provider selector as it is already.
Thanks,
Natti
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.
Update Local Tests updates affects only 'opt-in' Execution Servers
Include Execution Server Name for execution Activities
support for token based private code repos (Gitlab/Github)
Allow Data Type - Session to be passed as Output in Job Scheduler
Run “Update Local Tests” process automatically
Support "Retrieve Logs from reservation" feature w/ multiple exec server in exec server selector)
Ability to get configuration script and parameters via API during setup
Need a way to add execution servers based on reservations and capacity needs for execution