You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once we have metadata parsing for library item name/configuration finalize, I'd like to add to the metadata to be able to assign the library item to a blueprint from within the script or profiles metadata comments.
For the metadata format, we can either only allow the blueprint UUID or we could consider parsing the List Blueprints endpoint for the name of the blueprint and return the UUID that way. This works for classic blueprints and also assignment map blueprints, however, with assignment maps we also need the assignment node UUID, which doesn't have a name and would need to be retrieved from within Kandji and put into the metadata.
We also would need to consider how the removal of a library item from a blueprint process would work if a script or profile was assigned to a blueprint via metadata and then later that metadata for the blueprint was removed since the blueprint id would no longer be available within the metadata which is required for removal.
The text was updated successfully, but these errors were encountered:
Once we have metadata parsing for library item name/configuration finalize, I'd like to add to the metadata to be able to assign the library item to a blueprint from within the script or profiles metadata comments.
For the metadata format, we can either only allow the blueprint UUID or we could consider parsing the List Blueprints endpoint for the name of the blueprint and return the UUID that way. This works for classic blueprints and also assignment map blueprints, however, with assignment maps we also need the assignment node UUID, which doesn't have a name and would need to be retrieved from within Kandji and put into the metadata.
We also would need to consider how the removal of a library item from a blueprint process would work if a script or profile was assigned to a blueprint via metadata and then later that metadata for the blueprint was removed since the blueprint id would no longer be available within the metadata which is required for removal.
The text was updated successfully, but these errors were encountered: