Skip to content

Conversation

S3Prototype
Copy link
Collaborator

@S3Prototype S3Prototype commented Oct 2, 2025

This PR likely doesn't fix all indentation issues in our yaml snippets, but it does clean up the worst of the worst

It also removes pnpm run fmt from package.json because we have no intended formatting logic yet, and I don't want anyone running those commands thinking we endorse whatever they'll do to the repo yet

Add some pretier stuff

Update .prettierrc.json

Update .prettierrc.json

Update .prettierrc.json
@sg-writer sg-writer requested a review from joelhans October 2, 2025 17:22
@S3Prototype S3Prototype requested a review from sg-writer October 2, 2025 17:29
@sg-writer sg-writer added kind/bug Something isn't working docs/content Changes to the written material in the docs labels Oct 2, 2025
@S3Prototype
Copy link
Collaborator Author

@sg-writer Ready for another look

Copy link
Contributor

@joelhans joelhans left a comment

Choose a reason for hiding this comment

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

Found a few places where the indentation isn't quite right, or uses tabs instead of spaces. Overall this is a massively important fix, TY!

Comment on lines +72 to +73
... certificate ...
-----END CERTIFICATE-----
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be indented out further so that it matches with the dashes around BEGIN CERTIFICATE. Hard to say in GitHub's editor here, but I think this is right?

Suggested change
... certificate ...
-----END CERTIFICATE-----
... certificate ...
-----END CERTIFICATE-----

Comment on lines +28 to +31
- actions:
- type: forward-internal
config:
url: https://b.internal
Copy link
Contributor

Choose a reason for hiding this comment

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

If we remove the YAML formatter check, we need to start being careful that we're using spaces for indentation, not tabs. This policy doesn't work if you paste it into a cloud endpoint because of the tabs.

- name: good email
expressions:
- actions.ngrok.oauth.identity.email.endsWith('@ngrok.com')
- actions.ngrok.oauth.identity.email.endsWith('@ngrok.com')
Copy link
Contributor

Choose a reason for hiding this comment

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

This needs to be indented more.

Suggested change
- actions.ngrok.oauth.identity.email.endsWith('@ngrok.com')
- actions.ngrok.oauth.identity.email.endsWith('@ngrok.com')

- name: OAuth
actions:
- type: oauth
- type: oauth
Copy link
Contributor

Choose a reason for hiding this comment

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

This needs to be indented more, and then so does everything else nested beneath it.

Suggested change
- type: oauth
- type: oauth

- name: bad email
expressions:
- !actions.ngrok.oauth.identity.email.endsWith('@ngrok.com')
- !actions.ngrok.oauth.identity.email.endsWith('@ngrok.com')
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- !actions.ngrok.oauth.identity.email.endsWith('@ngrok.com')
- !actions.ngrok.oauth.identity.email.endsWith('@ngrok.com')

Comment on lines +218 to +220
- type: openid-connect
config:
issuer_url: https://accounts.google.com
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- type: openid-connect
config:
issuer_url: https://accounts.google.com
- type: openid-connect
config:
issuer_url: https://accounts.google.com

- name: Add JWT authentication and rate limiting
actions:
- type: rate-limit
- type: rate-limit
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- type: rate-limit
- type: rate-limit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs/content Changes to the written material in the docs kind/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants