[Esabora] Pouvoir pousser en ligne de commande un dossier peu importe l'état de synchronisation #2502
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.
Ticket
#2426
Description
Dans la commande
app:push-esabora-dossier
qui permet de pousser un dossier sans passer par la fiche signalementLorsque qu'on pousse un dossier unique via l'uuid du signalement et que la synchronisation a un statut à 0 cad colonne
is_synchronized
de la tableAffectation
, le dossier ne peut être pas poussé.Pour plus de souplesse, on devait pouvoir pousser ou repousser un dossier en ligne de commande peu importe son statut de synchronisation (la gestion des doublons est géré coté esabora)
Changements apportés
Pré-requis
Tests
make console app="push-esabora schs --uuid=00000000-0000-0000-2023-000000000012"
et vérifier que l'appel est toujours executéis_synchronized
en executant la requêteUPDATE `affectation` SET `is_synchronized` = '0' WHERE `affectation`.`id` = 18;
make console app="push-esabora schs --uuid=00000000-0000-0000-2023-000000000012"
et vérifier que l'appel est toujours exécutéis_synchronized
est toujours mis à jour à 1 après l'envoi du dossier