Skip to content
Snippets Groups Projects

Logging Enhancements for GCP modules (GONRG-1735, GONRG-1782)

Merged Artem Dobrynin (EPAM) requested to merge gcp-logging-enhancements into master
All threads resolved!
Files
34
+ 16
0
@@ -59,6 +59,18 @@ Each API is authorized by the following steps:
```
</details>
* **GET /entitlements/v1/users**. Retrieves all the members that are within the data partition provided in the _data-partition-id_ header. This API lists the direct members of the entitlements service with their list of groups and roles (excluding service accounts). **NB!** At the moment, this API endpoint only available in GCP-JDBC implementation of the Entitlements Service.
<details>
```
curl --request GET \
--url '/entitlements/v1/users' \
--header 'authorization: Bearer <JWT>' \
--header 'content-type: application/json' \
--header 'data-partition-id: osdu'
```
</details>
* **GET /entitlements/v1/groups/{group_email}/members**. Retrieves members that belong to the _group_email_ within the data partition provided in the _data-partition-id_ header. Sample _group_email_ value is `{name}@{data-partition-id}.{domain}.com`. The query parameter role can be specified to a filter group members by role of OWNER or MEMBER. In addition to authorization, the user or service extracted from JWT (email claim) in the _Authorization_ header is checked for membership within _group_email_ as OWNER or MEMBER. This API lists the direct members of the group (excluding hierarchical groups).
<details>
@@ -150,6 +162,10 @@ Instructions for running the GCP integration tests can be found [here][CGP docum
The database used in this implementation is PostgreSQL 13.0. The database structure and additional
info can be found [here][JDBC documentation].
### Integration test
You can use the same instructions for running the GCP integration tests to launch GCP-JDBC integration tests.
### Persistence Layer
The GCP implementation contains three mutually exclusive modules to work with the persistence layer.
Loading