-
Notifications
You must be signed in to change notification settings - Fork 37
feat: Cache OptimizelyConfig and set Pyyaml version #234
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
Conversation
2 similar comments
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.
Looks good. One missing test case is to validate OptConfig data updated correctly after datafile changes. Can we add it?
Added. Please check. |
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.
LGTM
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.
LGTM
@thomaszurkan-optimizely @msohailhussain I have fixed pyyaml version to 5.2 since the latest release only supports Python 2.7 or Python 3.5+. Have also updated the PR description. |
Summary
Optimizely Config cached in Config Manager. OptimizelyConfig should only be created on datafile update. Otherwise, Config Manager should return a cached copy.
Set Pyyaml version to 5.2 since the latest version 5.3 only works with Python 3.5+. And we need to run tests with Python 3.4 on Travis
Test plan
Issues
OASIS-5791