Restore content gaps flagged by registry/docs reconciliation - #575
Merged
Merged
Conversation
Each fix verified against the connector's actual source before applying. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
2 tasks
This branch was successfully deployed
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
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.
Summary
A registry/docs reconciliation pass (comparing each connector's registry stable-release docs against the live site) flagged 22 real content conflicts across the connector fleet. 8 of them needed source-level verification to determine which side was correct — this PR applies the 7 fixes that landed on the docs-site side. (The other verified fixes are being applied to the registry's stable release docs directly, outside this repo.)
pkg/connector/sts_federation_action.go.pkg/connector/teams.go(includes thevso.security_managescope requirement).CreateUserRequeststruct, which the site had trimmed down to 4 fields.Account -> Membershipstoken-permission bullets; confirmed still implemented inpkg/connector/access_rules_helper.go. Security/access-review-relevant, so flagging for extra scrutiny on review.BATON_WORKSPACESenv var; both described a v0.1.12 interim state that was fully reverted in PR Add user attribute push rules documentation #65 (tagged as the current stable v0.1.14), so neither is accurate anymore.ca_path/ca_pem,VAULT_CACERTprecedence).Test plan
🤖 Generated with Claude Code