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

docs: Better link language SDKs #6866

Merged
merged 2 commits into from
Jul 10, 2024
Merged

docs: Better link language SDKs #6866

merged 2 commits into from
Jul 10, 2024

Conversation

charlieegan3
Copy link
Contributor

The SDK support is there for many languages now and these are likely a preferred way to use OPA's REST API for many application developers.

This PR adds some links to make sure these are featured in suitable locations so they are not missed as people browse the docs.

The SDK support is there for many languages now and these
are likely a preferred way to use OPA's REST API for many
application developers.

This PR adds some links to make sure these are featured in
suitable locations so they are not missed as people browse
the docs.

Signed-off-by: Charlie Egan <charlie@styra.com>
Copy link

netlify bot commented Jul 9, 2024

Deploy Preview for openpolicyagent ready!

Name Link
🔨 Latest commit 1d1f860
🔍 Latest deploy log https://app.netlify.com/sites/openpolicyagent/deploys/668e5175e31dc20008196be6
😎 Deploy Preview https://deploy-preview-6866--openpolicyagent.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

When your application or service needs to make policy decisions it can query OPA
locally via HTTP. While it's possible to call OPA's [REST API](../rest-api) directly,
you can also find a number of [native language REST SDKs](/ecosystem/#languages)
eoo which make the integration easier.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has a weird typo in it -- "EEO"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😬 not sure what that one was meant to be...

OPA integration using one of the [language SDKs](/ecosystem/#languages) than working
with the REST API directly.
{{< /info >}}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find this note a bit misplaced. I mean we're on the rest api page and right at the top we're hinting that this approach may not be ideal. I would rather have this somewhere in the text later on or at the end imo.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The point is to ensure that users are aware that they dont have to deal with the REST API unless they need to.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've opted to move this down to the end of the intro, it still features prominently above the fold.

ashutosh-narkar
ashutosh-narkar previously approved these changes Jul 9, 2024
Signed-off-by: Charlie Egan <charlie@styra.com>
@charlieegan3 charlieegan3 merged commit 9bd7b5a into main Jul 10, 2024
28 checks passed
@charlieegan3 charlieegan3 deleted the sdk-linking branch July 10, 2024 09:21
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.

3 participants