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 >.
Yoav Ekshtein suggested an idea (#4006) · Sep 25, 2018 at 12:01 PM · shellserviceattributescloudshell 9.2
adding a custom attribute to a custom service shell results in an attribute that is not a user input.
that means that it creates an attribute that the user can't see in the portal , and I also can't change that property through resource manager (because it belongs to an invisible 2nd gen shell).
so effectively I don't see that anywhere (except via API)
Maya Ber commented · Sep 27, 2018 at 01:15 PM
Hi @Yoav.E,
Please check the below from the DevGuide https://devguide.quali.com/shells/8.3.0/customizing-shells.html, I'm copying here:
1) Add or modify an existing attribute as explained in the Customizing a Shell’s attributes section above.
2) If you want the service’s attribute to be exposed in the blueprint and sandbox, replace the tags line with the following:
tags: [user_input]
3) Save the shell-definition.yaml file, package and import the shell into CloudShell.
Yoav Ekshtein commented · Sep 27, 2018 at 01:24 PM
Hi Maya,
the process you mentioned above works for attributes I add via the shell-definition.yaml.
that is what I've ended up doing for my case...
in the Idea , I am talking about custom attributes (the non-namespaced kind), because the same attribute applies to a few different second-gen custom service shells.
right now this option exists for second-gen custom service shells , but is unusable because I can't see that attribute anywhere outside of the API.
thanks,
Yoav
Maya Ber commented · Sep 27, 2018 at 01:34 PM
Thanks Yoav. Could you please provide more information about what you're using this for, so I can get a sense of the use case? Or is the main issue that this option is still visible and only relevant to 1st gen (i.e. perhaps needs be removed)?
Yoav Ekshtein commented · Oct 02, 2018 at 07:36 AM
Hi Maya,
I needed it when adding an attribute to a few service shells and I didn't want to add the attribute individually to each custom shell. I was able to workaround (as was discussed in the previous comments) it but it meant triple work on that case.
I think that option for service shells makes sense and should be there, but without the user input flag it is not going to bring much value, as the user or admin can't interact with it (read, write, update or even see it exists) outside of the API.
thanks,
Yoav
Alona Getzler commented · Jan 01, 2019 at 01:06 PM
Hi, I'm happy to update this idea is in our backlog and planned for upcoming CloudShell releases.
Dan Michlin commented · Jun 02, 2019 at 12:58 PM
Hi I'm happy to update that this idea is included in CloudShell 9.2
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.
shells should come with execution server selector attribute as a default
Get resource context in initialize command if exists
Gen2 Service Shells need to be able to managed by Categories
Add custom attribute to be a parameter in discover
Service links to remain available after the reservation completed
vCenter static VM connectivity without dvSwitches
As the World Adopts SDN so has Azure/Microsoft. We require a Driver for the Microsoft SDN SONIC.