Skip to content

Commit 4ea36b5

Browse files
authored
Add --force option to publish commands in firedrill.yml
Since the detector name set in the firedrill script is Juno, sending a publish without force would always assign the `detector_name` to Juno.
1 parent b61f814 commit 4ea36b5

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

.github/workflows/firedrill.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -96,8 +96,8 @@ jobs:
9696
- name: Publish messages
9797
run: |
9898
echo "Publishing messages..."
99-
docker exec publishing_tools_publisher snews_pt publish /app/snews_pt/test/firedrill_combined_message.json --firedrill
100-
docker exec publishing_tools_publisher snews_pt publish /app/snews_pt/test/firedrill_combined_message2.json --firedrill
99+
docker exec publishing_tools_publisher snews_pt publish /app/snews_pt/test/firedrill_combined_message.json --firedrill --force
100+
docker exec publishing_tools_publisher snews_pt publish /app/snews_pt/test/firedrill_combined_message2.json --firedrill --force
101101
sleep 10
102102
103103
- name: Verify alert publishing from coincidence_system
@@ -180,4 +180,4 @@ jobs:
180180
fi
181181
echo "db_pipeline is still running and has not stopped or completed."
182182
echo "current db_pipeline docker logs:"
183-
docker logs db_pipeline
183+
docker logs db_pipeline

0 commit comments

Comments
 (0)