-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Remove readOnly attrs from Clients Count Config Serializer #21391
Conversation
…github.com/hashicorp/vault into ui/VAULT-17404/client-count-config-cleanup
normalizeResponse(store, primaryModelClass, payload, id, requestType) { | ||
if (!payload.data) { | ||
// CBS TODO: Remove this if block once API is published |
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.
This is actually needed, we confirmed
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 tackling!
Co-authored-by: claire bontempo <68122737+hellobontempo@users.noreply.github.com>
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 picking this up and modernizing the serializer! 🎉
I noticed in the flashMessage displayed after saving the config that the three attrs were mentioned. These are readOnly and thus do not need to be serialized. This is related to the census config work.
While I was in there, I "octane'ified" the serializer.
Backporting to last three supported versions, which misses the 1.11 which had this change. But this was not a functional bug, just cosmetic, so I think that is okay.