Add option to tag the source of a REST API request
Mor Paz - Port team
Today when a request is to made to Port's API using a standard API call (meaning, not with an integration), the Port user info in Port just shows Rest API.
As customer usage of Port increases, they are likely to have more than a single backend that makes requests to Port API to send information, and it would be helpful to tag the source of each of those requests so that they appear in the audit log in a clear manner.
An alternative could be multiple Client ID and Secret pairs, which each can be tagged as a specific "app" with it's own label in the Port user info column
T
Tomas Kratky
Would it be also possible to introduce a new "data_source" property or something similar so the requests would show up under separated data sources? The idea is to have multiple data sources for the REST API approach, like "Rest API - incident updater", "Rest API - k8s resources updater", and so on. It would help us identify whether some custom "exporters" or updaters touch specific blueprints, if they work correctly, what's the impact if we disable or modify them + the audit log would be separated by design.
N
Nick Amato
Seems like you beat me to it but I also made this here. https://roadmap.port.io/ideas/p/ability-to-specify-the-source-of-an-api-change-updatedbyalias-createdbyalias
N
Nick Amato
This would be enormously helpful for data provenance/lineage purposes. We have multiple areas that the REST API is used, so just seeing "REST API" isn't specific enough for us to troubleshoot issues with missing/incorrect data.