File ingestion - JQ manipulation
planned
Zbigniew M (ferror)
Currently, you can ingest files using the format
file_property: file://composer.lock
Being able to apply JQ at the file ingestion stage, will allow you to ingest less data to Port for a cleaner and faster portal, for example:
file_property: file://composer.lock | .myProperty
G
Gur Shafriri
planned
Time has passed, but we are now designing the solution for this.
The current plan is to add a "file" kind, supporting querying json or yaml files with JQ/YK, for one of the two:
- setting entity property based on the file content
- creating new entities based on the file content
S
Sebastien Foo
We could also set meta-properties such as $team from the content of any yaml file
S
Sebastien Foo
great request,
It will also help ingesting specific customer (like we have at Qlik) data model. We already have our own data model around yaml files.
We have one file at the root of the repo that contains the component (similar to a service) name, slacks channels, teams, champions, and also some other metadata used by our CI/CD. I was able to load this file using one property and then use "Calculation" fields types.
But we have also a separate yaml file to define Component dependencies.
here is an example of the componentDendencies.yaml file
components:
- component-a
- component-b
and for this I cannot use "calculation" fields.
So this requests would be a fantastic improvements, not only for "properties" but also for "dependencies" settings.