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

TT-10137 refactor: Remove TYK_GW_OPTIMISATIONSUSEASYNCSESSIONWRITE setting #119

Merged
merged 2 commits into from
Oct 9, 2023

Conversation

jakub-bochenski
Copy link
Contributor

I believe this is obsolete, see TykTechnologies/tyk-docs#3279

@jakub-bochenski jakub-bochenski requested a review from a team as a code owner September 21, 2023 17:17
@jakub-bochenski jakub-bochenski requested review from andrei-tyk and removed request for a team September 21, 2023 17:17
Copy link
Member

@buraksekili buraksekili left a comment

Choose a reason for hiding this comment

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

Yes. this is obsolete configuration in Tyk Gateway. The new versions of gateway (v2.7+) do not require such configuration for session writes. LGTM!

@caroltyk caroltyk changed the title refactor: Remove TYK_GW_OPTIMISATIONSUSEASYNCSESSIONWRITE setting TT-10137 refactor: Remove TYK_GW_OPTIMISATIONSUSEASYNCSESSIONWRITE setting Oct 3, 2023
@jakub-bochenski
Copy link
Contributor Author

I don't think the test failures are related to this change. Can this be merged?

@komalsukhani
Copy link
Collaborator

@jakub-bochenski You are right. Tests failure are not related to your change. They are using secret which doesn't exists on your repo that's why they are failing.

We merge the PR after QA test it. I will move your PR in the QA's backlog. Once we get green flag from QA we will merge it.

@singhpr singhpr merged commit ac53055 into TykTechnologies:main Oct 9, 2023
8 of 9 checks passed
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.

4 participants