-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI-1103: Fix #1558: Notification arg formats #1567
Conversation
@danepowell thanks for picking this up! This does exactly what I'm looking for and will eliminate a lot of complexity in my CI processes (: I think there is just one small issue to address -- if I give
If that can be avoided it will just end up at the generic "Notification format is not one of UUID, JSON response, or URL" which seems fine. |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #1567 +/- ##
============================================
+ Coverage 91.75% 91.77% +0.02%
- Complexity 1657 1663 +6
============================================
Files 110 110
Lines 5942 5957 +15
============================================
+ Hits 5452 5467 +15
Misses 490 490
☔ View full report in Codecov by Sentry. |
Thanks for the feedback! I fixed that and a few other bugs. Feel free to hammer on the new version, otherwise I'll merge this after getting coverage up. |
Motivation
Fixes #1558
Proposed changes
Anywhere that a notification UUID is required as argument, support passing a notification object or URL as well. This basically generalizes the
getNotificationUuid
logic in app:task-wait to all commands.Testing steps
./bin/acli ckc
acli app:task-wait
with various forms of arguments to ensure they still work:@cdubz could you please help test and let me know if it satisfies your request? If you follow the steps above, you can find a pre-built version of CLI for this PR to test with, or you can build it yourself.