fix(userAttributeProfiles): handle 403 if feature is not enabled #1181
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.
🔧 Changes
Implements a check as to whether the call to retrieve user attribute profiles returns a 403 and return null if so to ensure that tenants without the feature enabled still function without ignoring this resource type.
I have not added the check onto the call in
selfServiceProfilesbecause that explicitly requires adding the property which feels fair to fail on to me.📚 References
🔬 Testing
Added test and tested manually against tenant
📝 Checklist