Alias - new property type in blueprints
complete
Matar Peles
Today we can only relate between entities using the entity identifier.
Using aliases, you can give the entity an alias name, and use that alias on a relation.
That way, when you give the relation an alias, Port will relate between the source entity and all the entities with the same alias.
G
Gur Shafriri
Merged in a post:
Define relations based on search queries
David - Port team
Currently in order to create a relation between two entities, the identifier of the related entity needs to be specified. This means that the identifier of the related entity needs to be available as part of the entity reporting.
For example, when adding a new deployment to the catalog, the identifier of the related service needs to be specified as part of the relation.
We would like to improve the relation creation by enabling you to use queries instead of specifying the identifier.
For example, creating a relation between the "Frontend" service and all the Jira tickets with the "Frontend" label.
G
Gur Shafriri
complete
We didn't add aliases but went beyond it - you can now set relations based on search queries. You don't need to define an alias ahead of the mapping, use any property to define the relation.
Jonathan Gruber
This would include having the ability to have a property as an alias of an Entity to create relations
T
Thomas Moe
That would be incredibly helpful!
David - Port team
open
David Levy
David - Port team
what's the "open" status means?
is there any estimation for this issue?
David - Port team
David Levy Hi 🙂
We are currently investigating a few alternatives for significantly improving the experience of defining relations by using aliases or other solutions. Though the solution specifics are yet to be determined, you should expect it to be released during this quarter ✨
Please let me know if you have any additional questions.
David Levy
David - Port team estimations is my only question :)
i'm going to create a "gitlabUser" entity which will use the gitlab user id or username as identifier, but i would prefer to create a "user" blueprint with an alias identifier of gitlab user id.
David - Port team
David Levy:
Thank you for the additional details! I understand the use case, we are considering scenarios such as those you described when designing the right solution