Send autocomplete shadow traffic to the new EKS Api. #491
Conversation
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
| intsch.fetchAutocompleteSuggestions({ | ||
| query, | ||
| }), | ||
| ctx.vtex.production ? 1 : 100, |
There was a problem hiding this comment.
Implement: should only send 1% of the traffic from Prod to the new API.
salesfelipe
changed the title
| } | ||
|
|
||
| if (!hasError1) { | ||
| return result1 as T |
There was a problem hiding this comment.
We are still using the results from the I/O app
| expect(response).toEqual(result) | ||
| }) | ||
|
|
||
| it('should still function if the new client fails', async () => { |
There was a problem hiding this comment.
Validating that the errors on the new API shouldn't block the production request
| expect(ctx.vtex.logger.error).not.toHaveBeenCalled() | ||
| }) | ||
|
|
||
| it('should log if the results are different', async () => { |
There was a problem hiding this comment.
Validating that the log is working
salesfelipe
changed the title
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
What problem is this solving?
How should this be manually tested?
Workspace
Checklist/Reminders
README.md.CHANGELOG.md.Screenshots or example usage
Type of changes
Notes