[TECH] Logger et prévenir le crash de container lorsque la création de release est en échec #10483
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
|
Une fois les applications déployées, elles seront accessibles via les liens suivants :
Les variables d'environnement seront accessibles via les liens suivants : |
Mefl
approved these changes
Nov 5, 2024
HEYGUL
approved these changes
Nov 5, 2024
laura-bergoens
added
Tech Review OK
🚀 Ready to Merge
and removed
👀 Tech Review Needed
labels
pix-service-auto-merge
force-pushed
the
tech-log-and-prevent-from-crash-unsuccessful-release-creation
branch
from
3e04ad9 to
0c8387f
Compare
nlepage
approved these changes
Nov 5, 2024
pix-service-auto-merge
force-pushed
the
tech-log-and-prevent-from-crash-unsuccessful-release-creation
branch
from
0c8387f to
210b312
Compare
pix-service-auto-merge
deleted the
tech-log-and-prevent-from-crash-unsuccessful-release-creation
branch
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.
🍂 Problème
Lors d'une erreur retournée par l'API sur la route de création de releases, elle n'était pas retenue par l'API pix et le usecase continuait son chemin tranquillement
🌰 Proposition
Catcher l'erreur et logger et sortir
🎃 Remarques
🪵 Pour tester