-
Notifications
You must be signed in to change notification settings - Fork 179
fix: catch feature_not_enabled via err.body.errorCode and 400 status in organizations handler #1482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
dc386b8
fix: catch feature_not_enabled via err.body.errorCode and 400 status …
harshithRai b1bc48f
Merge remote-tracking branch 'origin/master' into DXCDT-2295
harshithRai 7f18357
fix: log real error code (e.g. insufficient_scope) when skipping org …
harshithRai 132b1f5
format: fix formatting
harshithRai 154b9c4
Merge remote-tracking branch 'origin/master' into DXCDT-2295
harshithRai File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The diagnosis on err.body.errorCode is spot on. One thing I wanted to check with you, the first branch
err?.statusCode === 403returnstruefor any403regardless of what the error code is. So a 403 with errorCode: 'insufficient_scope' (M2M app missing a required scope) wouldalso be caught here and logged as "Org-to-app entitlement is not enabled", which could send the operator down the wrong path
I know this broad
403catch was already there before this PR, so not something you introduced. But since we're refactoring this into a helper anyway, would it make sense to tighten it here?Since
err?.body?.errorCode === 'feature_not_enabled'already handles both400and403carrying the right errorcode, the status check seems redundant. Something like:
Or if you'd prefer to be explicit about which status codes are expected:
Happy to hear your thoughts on this, maybe there's a reason to keep the status only check that I'm missing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed. Tightened away from the raw 403 assumption. The log now reports the actual error code instead of always saying the feature is off, so a 403 insufficient_scope no longer gets mislabeled.