Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Adopt GraphQL #255

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

feat: Adopt GraphQL #255

wants to merge 1 commit into from

Conversation

OUeland
Copy link
Contributor

@OUeland OUeland commented Feb 7, 2022

No description provided.

@OUeland OUeland requested review from sasjo and a team as code owners February 7, 2022 12:56
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 7, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@mdovhopo
Copy link
Contributor

mdovhopo commented Feb 7, 2022

There was a problem related to GraphQL + OPA auth. There is no way (right now) to make secure requests with granular permissions for different Entities... Is there any solutions for that?

@OUeland
Copy link
Contributor Author

OUeland commented Feb 7, 2022

Yes, we have rules defined for access to individual entities in each GraphQL API. This is set up with OPA and managed by Styra.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants