Criteria	Usage
Questions with keyword1 or keyword2	keyword1 keyword2
Questions with a mandatory word, e.g. keyword2	keyword1 +keyword2
Questions excluding a word, e.g. keyword2	keyword1 -keyword2
Questions with a specific tag and keyword(s)	+[tag1] keyword1
Questions with two or more specific tags and keyword(s)	+[tag1] +[tag2] keyword1
To search for all posts by a user or all posts with a specific tag, start typing and choose from the suggestion list.

Nahum Timerman suggested an idea (#432) · Jul 26, 2016 at 11:54 AM · driver

provide cloudshell version in driver command context

Developers may need to make different implementations depending on cloudshell version. Provide version as part of command context object this would allow developers to perform develop backward compatible implementations by doing: if context.cloudshell_version=='7.0.0': implementation_a() ...

luiza.n commented · Jul 26, 2016 at 12:44 PM

Sounds great.

Gal Grossman commented · Jul 26, 2016 at 12:47 PM

great thanks

Yaroslav Nikonorov commented · Jul 26, 2016 at 01:07 PM

Good idea, or may be better to add supported_cloudshell_version to the driver itself, and check before installing environment.

0 · Show 1

Nahum Timerman · Jul 26, 2016 at 01:26 PM 0

Good point - with your suggestion we wouldn't run into situations were shells are used in unsupported cloudshell versions

Boris Modylevsky commented · Jul 26, 2016 at 01:38 PM

Generally it might be a good idea to expose the current version of the Cloudshell. However using it in order to determine whether a specific capability is supported sounds not the best technique. Alternatively, we can provide list of capabilities with meaningful names that are supported by cloudshell. For example: if context.supports_concurrency:

0 · Show 1

Nahum Timerman · Nov 14, 2016 at 02:40 PM 0

wow, I like this idea :) duck typing instead by static version

Ronen Akri commented · Aug 21, 2016 at 09:04 AM

Maybe this should be in the API rather than the context? This information might be useful when creating anything that interacts with the API, not just drivers and you would probably need it most when using the API.

Alon Saggie commented · Nov 16, 2016 at 06:31 PM

There's also a need for an Environment Command developer to know the Standard version that was used by the Shell's developer, to be able to handle different API signatures that sometimes are being changed between the standards versions.

Meni Beso commented · Feb 28, 2017 at 12:30 PM

This idea is planned to be implemented in CloudShell 8.0 GA.

Alona Getzler commented · Aug 03, 2017 at 06:34 AM

This idea was implemented in CloudShell 8.1. We added the following properties to driver contexts:
1) cloudshell_version was added to the ConnectivityContext
2) shell_standard and shell_standard_version was added to the ResourceContextDetails in case the resource model is associated with a 2nd gen shell.

Announcements >
CloudShell >	TestShell >
Developers >	BI (Business Inteligence) >

CloudShell's Dev Guide >	Configuration Management >
Getting started with Shells >	Extending CloudShell with Cloud Providers >
Getting started with Orchestration >	API Guide >

Announcements
CloudShell	TestShell
Developers	BI (Business Inteligence)

CloudShell's Dev Guide	Configuration Management
Getting started with Shells	Extending CloudShell with Cloud Providers
Getting started with Orchestration	API Guide

Welcome to Quali's Community Forums!

Quali's Idea Box!

Quali's Community Integrations

provide cloudshell version in driver command context

9 comments

Welcome to Quali's Community Forums!

Welcome to Quali's Idea Box!

Quali's Community Integrations

Your Opinion Counts

Follow This Idea

Related Ideas