lightspeed skill: document remediations:write 403 gotcha#128
Merged
Conversation
insights_fetch_remediation.yml fails with HTTP 403 if the service account only has Remediations viewer. Must have Remediations user role (remediations:remediation:write). Includes symptom, fix, and verify command. Verified 2026-06-16. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
insights_fetch_remediation.ymlfails with HTTP 403 when creating a remediation plan if the service account has only Remediations viewer. Documents the symptom, required role (Remediations user), and acurlverify command.🤖 Generated with Claude Code