Port in-product tile instructions for some OAuth integrations to the README that gets parsed inside the "Configuration instructions" section#23673
Draft
astorije wants to merge 1 commit into
Conversation
…README that gets parsed inside the "Configuration instructions" section
Contributor
Validation ReportAll 20 validations passed. Show details
|
astorije
commented
May 11, 2026
| - URL: `<BASE_URI>/oauth/auth?response_type=code&scope=signature impersonation organization_read&client_id=<YOUR_INTEGRATION_KEY>&redirect_uri=<YOUR_REDIRECT_URI>` | ||
| - `<BASE_URI>`: Use `https://account-d.docusign.com` for Developer or `https://account.docusign.com` for Production. | ||
| - `<YOUR_INTEGRATION_KEY>`: Replace with your Integration Key (Client ID) obtained previously. | ||
| - `<YOUR_REDIRECT_URI>`: Replace with your redirect URI, e.g., `http://localhost/`. |
Contributor
Author
There was a problem hiding this comment.
I believe all of this is outdated since Docusign is an OAuth integration.
astorije
commented
May 11, 2026
| 3. Click **Add integrations**. | ||
| 4. Search for Datadog and click on the tile. | ||
| 5. Click **Install**. | ||
| 6. Navigate to Datadog, then log in. |
Contributor
Author
There was a problem hiding this comment.
I understand this section is now obsolete, but correct me if I'm wrong.
astorije
commented
May 11, 2026
|
|
||
| ## Setup | ||
|
|
||
| ### Generate API Credentials in RingCentral |
Contributor
Author
There was a problem hiding this comment.
I believe all of this is obsolete now that RingCentral is an OAuth integration.
apiazza-dd
approved these changes
May 12, 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.
What does this PR do?
This merges the content of the tiles back into the README which are the source of truth.
Motivation
There is ongoing effort to auto-generate OAuth integrations and part of this requires pulling the "configuration instructions" from these README files.
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged