docs(netsuite): clarify certificate key pair generation steps#617
Merged
Conversation
Customer feedback (Pylon #1452) noted that the section assumed terminal familiarity. Restructure step 5 into labeled sub-steps with explicit "open a terminal in this folder" instructions per OS, clarify that the openssl certificate prompts can all be defaulted (the values aren't used by the integration), add a verification step pointing to where the .pem files land, and add a "just start over" troubleshooting note. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
laurenzlong
approved these changes
Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Customer feedback (Pylon #1452) noted that the section assumed terminal familiarity. Restructure step 5 into labeled sub-steps with explicit "open a terminal in this folder" instructions per OS, clarify that the openssl certificate prompts can all be defaulted (the values aren't used by the integration), add a verification step pointing to where the .pem files land, and add a "just start over" troubleshooting note.
Screenshot
Please include a screenshot of the documentation running locally with
cd src && mint dev.