Skip to content
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

Availability: Fixes get account info retry logic to not go to secondary regions on 403(Forbidden) #2511

Merged
merged 9 commits into from
May 29, 2021

Conversation

j82w
Copy link
Contributor

@j82w j82w commented May 28, 2021

Pull Request Template

Description

This fixes a bug where if a user gets a 403(Forbidden) exception the SDK will try to go to the secondary regions. It will also now throw an aggregate exception if there are multiple failures instead of just throwing the last. This needed because it's possible the last failure maybe different then the cause of the other failures.

Type of change

Please delete options that are not relevant.

  • [] Bug fix (non-breaking change which fixes an issue)
  • [] New feature (non-breaking change which adds functionality)
  • [] Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • [] This change requires a documentation update

Closing issues

To automatically close an issue: closes #2496

Co-authored-by: Matias Quaranta <ealsur@users.noreply.github.com>
@j82w j82w merged commit e44f9fc into master May 29, 2021
@j82w j82w deleted the users/jawilley/ha/aad_retry branch May 29, 2021 01:38
@ealsur ealsur changed the title Availability: Fixes get account info retry logic to not go to secondary regions on 401(Forbidden) Availability: Fixes get account info retry logic to not go to secondary regions on 403(Forbidden) Aug 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants