Using RT and NQ Production Endpoints for SMC #485
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Because of resources, we need to use the data bot in production environment to generate the data for SMC, so now we will consume those endpoints
|
Check PR 485 preview 👀 |
diegopf
approved these changes
May 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because of resources, we need to use the data bot in production environment to generate the data for SMC, so now we will consume those endpoints
Pull request template
I have changed the hardcoded URLs for related tags and next queries to use production endpoints (already working) instead of staging endpoints.
Motivation and context
The motivation was that we needed the bot to be able to consume more resources so he could ingest our feed. Instead of changing it for all staging clients, we will use the instance on production environment as that one already has the needed resources.
Type of change
What is the destination branch of this PR?
MainHow has this been tested?
I have already tested the endpoints. They contain information in the same format as staging and the URLs I wrote are correct