API for editing blueprints without re-packing them

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.

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.

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.

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.

@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.