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 >.
Kimo Saper suggested an idea (#4279) · Jan 08, 2019 at 04:35 PM · shelldocumentation
Read-Only attributes that are inherited into your Shell and basically obscured to a Developer until trying to update it throws an error.
Example here is the 'Bandwidth' attribute on the CS_Port model.
I'm using it on a Deployed App Shell, and had no way to really know that it was Read-Only short of digging through the mountain of included YAML files on the Server.
The API doesn't indicate that the attribute is currently readonly in any inquiry about the device. In fact you get no indication that it is set as ready only until you attempt to update it. Currently I embedded the process into the Cloud Provider's Shell 'remote_refresh_ip' command, and I'm already traversing the built networking in it's environment.
In addition, in the Published Shell Standards page, Bandwidth isn't even listed as an available attribute:
The ask is for some way to know prior to debugging a shell, or digging through the included YAML files, to know that an inherited attribute (or any attribute) is set to a 'Read-Only' status in a shell.
Alona Getzler commented · Jan 09, 2019 at 08:02 AM
Hi Kimo, thank you for posting this idea. The fact that the attribute isn't detailed in the published standard in github is a bug we will fix. The standard documentation page should be your source of information for the attributes that come with the standard and what rules are defined on them.
Regarding the "Read-Only" behavior - attributes that are marked as "Read-Only" are meant to be populated only by the get_inventory command on the resource discovery.
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.
Python 3 CloudShell Packages should feature Python 3 Type Hints following PEP 484 format
Allow the shell driver to set the Description field of a sub resource in Autoload
Networking shells file transfer protocol
Get resource context in initialize command if exists
Augment shell discovery via SNMP with a NetConf option
Net a Driver for Citrix/Netscaler devices
Gen2 Service Shells need to be able to managed by Categories
Cisco shells - Configre show cdp nei while setting up the vlan