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 >.
Hi,
I have a custom built switch shell and the 'ports' are searchable in the inventory, by default. Is there any way to set the ports as 'unsearchable' for this specific switch shell?. The ports should appear for a connection/route in the sandbox, but must not appear in the inventory search. Please advise. Thanks.
Regards
Geetha
Answer by Geetha Kuthalam · Sep 28, 2020 at 11:45 PM
Hi,
Can you please answer this question? thanks.
Regards
Geetha
Answer by Sadanand Hegde · Sep 29, 2020 at 11:33 AM
Hi Geeta,
As per switch shell standard, ports are searchable. Any shell inheriting the switch standard will have this property. So, I doubt this can be modified.
Regards,
Sadanand
Answer by Geetha Kuthalam · Sep 30, 2020 at 03:54 AM
Hi Sadanand,
Thanks for replying. It is disappointing to know that the property cannot be modified.
Regards
Geetha
Answer by Kimo Saper · Oct 02, 2020 at 08:06 PM
Another way would be via Domain/Group view privileges.
Most installations simply assign everyone and everything into 'Global' by default. And then add additional domains afterwards for additional restrictions. A better way to start this is to create an alternative "Global Domain" named for the company - in the case "ACME". So by default all resources are added to the "ACME" domain instead of the Global, and Groups have access to the ACME domain. So in practice, the entire switch/router would be added to the domain, then you could selectively remove any specific ports. You could also add any specific ports to an "Admin" domain (the parent also inherits this) so they are easily search for with in that domain only (Switch your scope of work to that domain).
This is a real advantage to not having/using the default "Global" Domain.
However, they will not be useable for the routes in that domain.
So you could create routes in an admin template or blueprint and leave them or map specific connections, but they will not be accessed.
But it could be replaced in the blueprint with a visual connection.
Also note that requesting a route does not change a hard mapped connection in Resource Manager.
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.
How do you add an attribute to a port on a resource created from 2nd Gen shells? 3 Answers
Need some examples of creating Curl Rest commands in a shell? 1 Answer
driver targeting different CloudShell version 3 Answers
Shell for CloudShell authoring driver 1 Answer
GitHub packages failing unit tests 1 Answer