Fixed unmarshalling error when IP Allowlist is configured on viridian #339
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
✅ Deploy Preview for eclectic-sawine-19fcf1 canceled.
|
2023-08-11T19:47:32.962+0100 ERROR viridian/common.go:228 listing clusters: json: cannot unmarshal array into Go struct field Cluster.Content.allowedIps of type string
Here's an example grabbed from the Viridian UI
{id: 177, ip: "207.154.227.247", description: null}
pmcgleenon
force-pushed
the
viridian-allowedips
branch
from
767d42d to
d3a35ff
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Here's the log message from
clc viridian list-clusterswhen a cluster has an IP Allow list configuredHere's an example of what the IP looks like from the Viridian
/cluster/endpoint - grabbed from the Viridian UI{id: 177, ip: "207.154.227.247", description: null}