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

Use a role cache to avoid separate locking paths #6926

Merged
merged 5 commits into from
Jun 20, 2019
Merged

Commits on Jun 19, 2019

  1. Use a role cache to avoid separate locking paths

    Due to the various locked/nonlocked paths we had a case where we weren't
    always checking for secondary status before trying to upgrade. This
    broadly simplifies things by using a cache to store the current role
    values (avoiding a lot of storage hits) and updating the cache on any
    write, delete, or invalidation.
    jefferai committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    c2b9a6f View commit details
    Browse the repository at this point in the history
  2. Update role crud test

    jefferai committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    d4d2d91 View commit details
    Browse the repository at this point in the history
  3. Update builtin/credential/aws/path_role.go

    Co-Authored-By: Vishal Nayak <vishalnayak@users.noreply.github.com>
    jefferai and vishalnayak authored Jun 19, 2019
    Configuration menu
    Copy the full SHA
    8cdc06c View commit details
    Browse the repository at this point in the history
  4. Set role cache on read

    jefferai committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    07eb397 View commit details
    Browse the repository at this point in the history
  5. Fix compilation

    jefferai committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    4a45122 View commit details
    Browse the repository at this point in the history