Update notificationBlockList
to support new API warning messages format
#13107
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.
Summary
Rancher
head
recently introduced API changes, previous version isv2.11-2053ce644a31cd8053d1f58e2487154b0b8513b6-head
see #13111The format of warning messages in PUT response headers has changed:
299 - unknown field "id"
has become299 - "unknown field "\id\""
The PUT requests now send the warnings for fields we are sending in the PUT requests that are not expected.
Some fields are missing from the response:
id
,links
,type
.Warnings are notified by growl dialogs. We should consider if this is the right approach or switch to console warnings
Occurred changes and/or fixed issues
Technical notes summary
Fixing point 1 in description.
We need to investigate whether the other points have an impact on the UI
Areas or cases that should be tested
Areas which could experience regressions
Screenshot/Video
Checklist