Replies: 1 comment
-
Hi @ave165, Thanks for reaching out! It’s great to hear you're using Microcks, and your question suggests that you might be utilizing it on a large scale. Regarding your points: 1/ Identifying Mock Owners: Assign the admin role exclusively to mock owners for easy identification. Use labels to tag them as "owners" (similar to how teams are organized in the documentation). For details, refer to the doc here: Organizing Repository. To retrieve a list of all owners, you can query labels via the Microcks API by using the /services/labels endpoint, which is outlined in the API documentation. This list can then be used as needed. Note that these labels are also visible in our Backstage plugin, which enhances integration. For more on this, check the Backstage integration blog post: Backstage Integration Launch. 2/ Tracking User Access: There’s no built-in authentication tracking for tracing mocks users generated by Microcks. For this purpose, an external authentication layer can be implemented before accessing the mock services, allowing you to monitor, report and control user access effectively. Hope this helps! Please keep us updated. |
Beta Was this translation helpful? Give feedback.
-
Hi TEam,
Is there a way to extract data around who built what mock api, basically we want a feature where we want to know the owner of the mock api, and also the users who are using it.
Thanks
Abhinav
Beta Was this translation helpful? Give feedback.
All reactions