Enable appending to objects / arrays on ingestion
complete
Matar Peles
Today, when updating new objects / arrays of entities the new value overrides the old one. With this feature it will be possible to append values to these properties.
Example of Tags property with type of array:
Current state:
"Tags" : ["tag1"]
Ingesting a new tag using the API:
"tag2"
New state:
"Tags": ["tag1", "tag2"]
M
Maya Margalit
updated the status to
complete
Appending values to an array property is now supported!
For more info please check our docs:
https://docs.port.io/context-lake/data-model/setup-blueprint/properties/array/#multi-sources-ingestion
Clarification: currently supported only in array property, not relation.
Photo Viewer
View photos in a modal
R
Richard Rein Jr
Maya Margalit It looks like multi-source ingestion is only supported for arrays of strings and numbers, not objects - so my use case below (ingesting all related references/scripts/assets for a skill via GitOps) is not supported yet, correct?
M
Maya Margalit
Richard Rein Jr You are right, in our docs, the suggested data model for skills uses object array for references and assets, and we currently only support appending values to arrays of strings and numbers.
We plan to support objects array too, in the next phase of this feature.
If this is an important capability for you I recommend to create a new feature request here in Canny of supporting the multi source ingestion in objects arrays too. This way you can track it and get notified once it's supported too.
R
Richard Rein Jr
Maya Margalit Added here
R
Richard Rein Jr
I am curious if this would also potentially cover the use case of ingesting all related references/scripts for a skill, like when attempting to build out a skill registry based on skills stored in one or more repos? (Specifically, we are looking to import skills via an Azure DevOps integration, following this model)
M
Maya Margalit
updated the status to
in progress
S
Simon Beaulieu
Relevant use case: Being able to populate define 1:many relationships between entities during mapping from the point of view of the target.
For example, if I have a 1:many relationship between a Github repository and Github branches and I want the Github repository to be the source of the relationship, I cannot possibly know the identifier of all branches in advance. When mapping the branches, having the ability to update the relationship of a repository entity by appending all branch identifiers calculated from the "branch" kind.
This would also circumvent the current documented limitation of 100 results max when attempting to map using search queries.