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

GraphQl mutation state check | PlaceOrder and Customer actions - skip list adjustments #90

Merged
merged 3 commits into from
Mar 19, 2024
Merged

GraphQl mutation state check | PlaceOrder and Customer actions - skip list adjustments #90

merged 3 commits into from
Mar 19, 2024

Conversation

vpodorozh
Copy link
Contributor

@vpodorozh vpodorozh commented Feb 20, 2024

Description (*)

  • Exclude Ealsticsearch classes from mutation state check, as they are going to be used for product reindexation need once indexer state is set OnDemand.
  • Exclude Redis client and logger classes from mutation state check for customer create&update operations. Session start with redis is tightly coupled yet with any customer related activity - even in GraphQl. I assume that is in TODO list to resolve by Adobe engeneers.

Fixed Issues

#82

…y are going to be used for product reindexation need once indexer state is set OnDemand.
@vpodorozh vpodorozh requested a review from a team as a code owner February 20, 2024 09:14
…ate operations. Session start with redis is tightly coupled yet with any customer related activity - even in GraphQl. I assume that is in TODO list to resolve by Adobe engeneers.
@vpodorozh vpodorozh changed the title GraphQl mutation state check | Place Order - exclude Elasticsearch classes GraphQl mutation state check | PlaceOrder and Customer actions - skip list adjustments Feb 20, 2024
…ate operations. Session start with redis is tightly coupled yet with any customer related activity - even in GraphQl. I assume that is in TODO list to resolve by Adobe engeneers.
@Vinai Vinai merged commit 8f79520 into mage-os:2.4-develop Mar 19, 2024
7 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.

2 participants