fix(lxc): unmarshal string/int vmid as int when read container status #622
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.
Contributor's Note
/docs
for any user-facing features or additions./example
for any new or updated resources / data sources.make example
to verify that the change works as expected.The PR fixes an unmarshal error of the returned vmid of an LXC container
nodes/{node}/lxc/{vmid}/status/current
.There is an existing types.CustomInt common type that already implements the correct un/marshal interfaces.
Those common types do not appear to be unit tested but I figured they're around since a while.
It would probably be better to add some container_types_test.go for it though.
Not sure how the PVE REST API deals with the a vm as opposed to an LXC container but the fix might apply there as well.
Proof of Work
Before:
After:
Community Note
Closes #621