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

Adds Rego capabilities page #1543

Merged
merged 5 commits into from
Aug 2, 2024
Merged

Conversation

ZPain8464
Copy link
Contributor

This PR:

  • Adds a new Custom Rego Policies capabilities page.
  • Alphabetizes the ENT capabilities
  • Moves Rego support content to the new Rego page

Resolves https://github.com/pomerium/internal/issues/1874

@ZPain8464 ZPain8464 requested a review from a team as a code owner July 31, 2024 13:01
@ZPain8464 ZPain8464 requested review from cmo-pomerium and removed request for a team July 31, 2024 13:01
Copy link

netlify bot commented Jul 31, 2024

Deploy Preview for pomerium-docs ready!

Name Link
🔨 Latest commit 73f3ed0
🔍 Latest deploy log https://app.netlify.com/sites/pomerium-docs/deploys/66accfa1591aec000858b048
😎 Deploy Preview https://deploy-preview-1543--pomerium-docs.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.

Copy link
Contributor

@kenjenkins kenjenkins left a comment

Choose a reason for hiding this comment

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

Looks good, just one comment.


This example pulls session data from the Databroker service using `type.googleapis.com/session.Session` for users and `type.googleapis.com/user.ServiceAccount` for service accounts.

::::enterprise
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we don't need a second Enterprise admonition here if there's already one at the top of the page. That would also allow us to avoid nesting a "Note" admonition inside another admonition.

What about moving this information up, before the "Outputs" section heading?

Copy link
Contributor Author

@ZPain8464 ZPain8464 Aug 2, 2024

Choose a reason for hiding this comment

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

Agreed. I went ahead and moved this section up, and removed the enterprise admonition wrapper.

@ZPain8464 ZPain8464 merged commit 59be08c into main Aug 2, 2024
8 checks passed
@ZPain8464 ZPain8464 deleted the zpain/add-rego-capabilities-page branch August 2, 2024 12:25
backport-actions-token bot pushed a commit that referenced this pull request Aug 2, 2024
* alphabetizes Enterprise capabilities

* migrates rego support content to new page

* fixes precommit failures

* fixes cspell

* moves enterprise admonition
ZPain8464 added a commit that referenced this pull request Aug 2, 2024
Adds Rego capabilities page (#1543)

* alphabetizes Enterprise capabilities

* migrates rego support content to new page

* fixes precommit failures

* fixes cspell

* moves enterprise admonition

Co-authored-by: zachary painter <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants