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.
Yaniv Kalsky suggested an idea (#3897) · Aug 08, 2018 at 10:41 AM · driverdevelopment
When you want to debug a driver from the IDE, you need a way to provide the context to the relevant command.
When working on scripts, you have the attach_to_cloudshell.
This piece is missing for resource drivers.
Alona Getzler commented · Aug 09, 2018 at 07:48 AM
Hi Yaniv, thank you for posting this idea. This makes perfect sense and we will consider adding that to our backlog.
Natti Katz commented · Dec 09, 2018 at 05:30 PM
Yoav and Adam rolled up a nice solution recently. I've been using it and it works great.
Just drop into your driver folder (or keep at shell root directory to keep credentials off the server).
Perhaps all the code can be wrapped up into a clean helper and added to script_helpers.
something like:
context = get_driver_context(user, password, domain, sandbox_id, server, resource name)
from cloudshell.helpers.scripts.cloudshell_dev_helpers import attach_to_cloudshell_as import cloudshell.helpers.scripts.cloudshell_scripts_helpers as sh from cloudshell.shell.core.driver_context import ResourceCommandContext import driver as mydriver attach_to_cloudshell_as( user='admin', password='<my_pass>', domain='Global', reservation_id="dbe44edf-1e0d-48d3-a447-e2761445cefd", server_address='localhost', resource_name="<my_resource_name>" ) session = sh.get_api_session() token = session.token_id reservation_context = sh.get_reservation_context_details() reservation_context.reservation_id = reservation_context.id connectivity_context = sh.get_connectivity_context_details() connectivity_context.admin_auth_token = token context = ResourceCommandContext( connectivity=connectivity_context, resource=sh.get_resource_context_details(), reservation=reservation_context, connectors='' ) # instantiate driver debug_driver_instance = mydriver.CustomShellDriver() # call methods debug_driver_instance.send_custom_mail(context)
Thanks for sharing Natti!
Although it's possible to solve it with such ways - the request here is to have it "built-in" with the driver helpers so that we won't have to re-invent this every time.
The script above is also mixing script helpers and driver context and does not solve the use case of service drivers.
There is a page in the dev guide regarding debugging using mocks - this can help as well in most cases.
https://devguide.quali.com/shells/9.0.0/debugging-shell-commands.html#gen2
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.
have an option , while developing a driver , to not load the virtual environment every time
Storing Reservation specific information for later use
RBAC for resource, blueprint commands
API call for creating a copy of an existing blueprint
Managing Cisco active-active pairs
Adding new drivers to existing devices
Shell for Ixia with Autoload Support
have a message when virtual environment is being created and when it finishes