Add monitoring to coveo token generation workflow #1288
Merged
Conversation
This file contains hidden or 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
github-actions
bot
added
the
tooling
✅ Deploy Preview will be available once build job completes!
|
lamATnginx
force-pushed
the
add/coveo-token-gen-monitor
branch
2 times, most recently
from
d75196d to
a2f0308
Compare
lamATnginx
force-pushed
the
add/coveo-token-gen-monitor
branch
from
a2f0308 to
00712a9
Compare
lamATnginx
force-pushed
the
add/coveo-token-gen-monitor
branch
from
dea9f9b to
ea6d6c0
Compare
lamATnginx
commented
Oct 10, 2025
nginx-jack
approved these changes
Oct 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Proposed changes
Add slack notification if any of the environments fail to generate a new coveo token.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩