-
Notifications
You must be signed in to change notification settings - Fork 1
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
Follow-on for dismissed deployment support PR #2524
Follow-on for dismissed deployment support PR #2524
Conversation
… fix) and spelling change of "cancelling" to "canceling"
…d filtering to include some log messages from connect which had the local ID value in snake_case rather than camelCase
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had a couple questions on this one, plus the issue with changing a vendor file.
Changes requested have been committed @dotNomad . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for those changes. Looking good 😎
…oyment-follow-on-2 Follow-on #2 for dismissed deployment support PR
…ent' into sagerb-support-dismissed-deployment-follow-on
0376c4d
into
sagerb-support-dismissed-deployment
Intent
Resolves: #2179
This PR contains follow-on changes to #2522. These changes have been separated in order to facilitate reviews in progress.
Type of Change
Approach
The changes contained within this PR are:
User Impact
The publisher log now looks like this when the deployment has been canceled:
Automated Tests
Added unit test for API, validating the expected behavior for success and 404.
Directions for Reviewers
Checklist