-
Notifications
You must be signed in to change notification settings - Fork 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
Rename fields on proxyConfig #15541
Rename fields on proxyConfig #15541
Conversation
@jorgemarey is attempting to deploy a commit to the HashiCorp Team on Vercel. A member of the Team first needs to authorize it. |
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.
Hi @jorgemarey and thanks a lot for raising this PR. While we get around to reviewing this, I wonder if it would be possible to add a changlog entry; we have this guide available detailing the format.
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.
Hi @jorgemarey and thanks again.
Unfortunately renaming an internal struct field will break the messagepack encoding we use to serialize to the state store. This means we therefore cannot accept a fix of this nature.
Hi @jrasell. I thought of that, but wasn't sure about it. Do you have any ideas of how to best solve this? |
Hi again, If this aproach doesn't work. How about chaning the API but making it compatible with the current format. It would be something like the following (we'll need to add the changes to the Path field also):
Basically, change the api field to be Expose (like in the struct field but checking if in the json the value ExposeConfig has content, and in that case use that. |
Hi @jrasell can you check the above? Seems to be a fix and this is quite a significant issue that is broken. |
Hi @jorgemarey sorry for letting this issue slip by - but yeah I think introducing the new field name while deprecating the old name but keeping it for compatibility sounds reasonable. We're expecting to ship 1.5-beta early next week so if we can get those changes in, that would be really great. |
Hi @shoenig , thanks for looking into this. I'll try to make the changes this weekend. |
d8a4e87
to
fbcccaf
Compare
Hi @shoenig, I think I made all the needed changes for this to work. |
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.
LGTM; thanks @jorgemarey!
* Rename fields on proxyConfig (manual backport of #15541) * fixup backport mistake --------- Co-authored-by: Seth Hoenig <[email protected]>
This renames two fields in the api for proxyConfig.
The old fields are mantained for backwards compatibility
Fixes #11304
Fixes #12174
Fixes #9379