Skip to content

Added steps explaining token cache on distributed environment #195

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 2 commits into from
Oct 30, 2019

Conversation

TiagoBrenck
Copy link
Contributor

@TiagoBrenck TiagoBrenck commented Oct 17, 2019

Purpose

Apps deployed on distributed environments need to tweak the token cache configuration to be adequate to this architecture. I have added a section exposing available solutions and a code snippet to each of them.

This PR would be an answer for this issue: #158

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

How to Test

To be able to test it, you will need 2 different apps deployed on Azure or 1 app with two deployment slots. You cannot test this locally.

What to Check

Verify that both apps are able to grab and save tokens from the cache without any exception being thrown.

Other Information

Resources gotten from:

Copy link
Contributor

@jennyf19 jennyf19 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

Copy link
Contributor

@jmprieur jmprieur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @TiagoBrenck
LGTM

@TiagoBrenck TiagoBrenck merged commit 42a1379 into master Oct 30, 2019
@TiagoBrenck TiagoBrenck deleted the tibre/deployImprovements branch October 30, 2019 00:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants