Support selector filter to use integration advanced mappings
T
Tom Tankilevitch
Ability to filter resources exported to port based on the integration advanced mapping.
Use case:
When exporting Gitlab repositories filter the repositories exported to port based on whether a file exists in the repository.
Currently gitlab mapping supports advanced mapping such as
search://
|| file://
as part of the entity mapping, but not in the selector filter which only supports jq.If we support search:// capability in the selector it would've solved that issue.
K
Kevin Law
I am experiencing the same. We sync yaml catalog files as the "service" blueprint, then sync the Gitlab projects over with the service relation.
That syncs 1000s of projects and takes about 2 days to run.
We filter the service catalog by
gitlab_repo != ""
so it exludes projects that don't have the yaml file. We'd love to filter the gitlab project sync to only contain the yaml file, that would help reduce the time it takes to sync everything