Skip to content

Conversation

@StamatisChr
Copy link
Contributor

Please go to the Preview tab and select the appropriate template:

@hashicorp-cla-app
Copy link

hashicorp-cla-app bot commented Oct 28, 2025

CLA assistant check
All committers have signed the CLA.

@hashicorp-cla-app
Copy link

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 28, 2025

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal ✅ Ready (Inspect) Visit Preview Tue Oct 28 18:57:08 UTC 2025
Unified Docs API ✅ Ready (Inspect) Visit Preview Tue Oct 28 18:50:54 UTC 2025

@github-actions
Copy link
Contributor

github-actions bot commented Oct 28, 2025

Broken Link Checker

No broken links found! 🎉

Copy link
Contributor

@trujillo-adam trujillo-adam left a comment

Choose a reason for hiding this comment

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

Thanks for updating this! I added a few grammar and style-related suggestions. Approving so you can move forward when ready.

@connorfryar
Copy link
Contributor

Added a couple of single line comment.

Context:
Providing the OpenSSL commands like we are already seems like a massive extension of an olive branch for our customers.

I think it would be appropriate to potentially change the names of the cert and the key to match the start up name requirements of TFE. cert.pem/key.pem.

Check single line comments for further clarity.

@connorfryar
Copy link
Contributor

LGTM

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.

3 participants