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 >.
George Rainovic suggested an idea (#3535) · Apr 27, 2018 at 11:47 PM · blueprintapiabstract resourceinputs
I'd like to have API to edit blueprints without re-packing them on ES filesystem.
I am interested in:
- changing Blueprint Inputs (Global & Additional Info),
- changing abstract resources in the blueprint, requirements and additional info
-----
Passing info about requested sw version as an abstract resource info is very nice concept.
Editing 50+ resources in the blueprint to add a new value of the attribute is not fun at all.
Alona Getzler commented · May 01, 2018 at 09:08 AM
Hi George, thank you for posting this idea.
First of all, I'm not sure I understand your editing blueprint flow and how removing the "re-pack"+"import" steps will help with the use cases you described. Can you elaborate?
Secondly, the use case of updating a new value for the SW Version input which affects 50+ abstract resources in the blueprint can be easily solved by linking the requirement or additional-info inputs of the abstracts to one global input that will be exposed to the user. More information about this can be found in the section "Grouping together resource requirements and information" in this help article.
Thanks,
Alona.
George Rainovic commented · May 10, 2018 at 05:54 PM
Hi Alona,
I wish we have a more direct way to change blueprints, without editing files on FS.
About linking Additional Info (AI) to Global Inputs (GI). My understanding is that if we want to add new value for the SW Version, we need to update not only GI, but AI for every single resource in the blueprint we want to use this SW Version.
***
We solved our problem by changes in our custom automation code in the drivers. The resource driver looks into the value of the AI, and if it finds GI with the same name, it takes value from that GI. Just another layer of indirection. For new SW Version, now user needs only one change, on one GI.
Alona Getzler commented · Jun 07, 2018 at 08:38 AM
Hi,
Thank you @grainovic for the detailed reply. Just to summarize, the main gap you raise here is the flow for editing the possible values list for published attributes (requirements, additional info, and their linked globals). For example, if there is a new SW version you need to add this option to the "SW version" attribute in the additional-info tab of all the abstract resource.
We will definitely consider implementing a solution to address this gap, which will give a more direct flow for editing published attributes in a blueprint.
I'm moving this idea to "Active". If anyone has additional info about this use case please comment and vote for this idea.
Thanks,
Alona.
Omri Avraham commented · Jun 12, 2018 at 08:30 PM
API for Global Inputs would be a great help.
As we have Global inputs based on the active inventory (i.e. system names). Everytime we inventory a new device or remove an old one, we have to manually update every blueprint Global input with the new possible values.
Francisco Rosas Soria commented · Jun 30, 2020 at 10:49 PM
@Inga Almagor This seems essentially the same thing as we talked about today. We'd like to be able to modify blueprints attributes (estimated teardown, global inputs) using an API without having to repack anything.
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.
API for editing abstract resource templates
Save sandbox as blueprint - include updated global inputs
Display set attribute pull down list of Global input(Lookup) by alphabetical order
Support for more than 1 in Quantity for connected abstract resources
DEFAULT Email Notifications PER blueprint
'Check Blueprint' as an API command
add sandbox context component to any blueprint script