fix: solved the agent spin-up with apiKey updation on org_agent table #417
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.
What
Resolves the agent spin-up issue by implementing a crucial apiKey update in the org_agent table.
Why
The agent spin-up problem was identified to be linked to outdated API keys stored in the org_agent table. This update aims to ensure that the API keys are consistently updated, thus eliminating the spin-up issue.
How
The update involves making necessary modifications to the org_agent table, ensuring that the apiKey field is updated appropriately during the agent spin-up process. This will result in improved functionality and a more reliable agent deployment process.