Bug: GraphQL API doesn't return shared_v4 IP address

1

When querying the GraphQL API directly for an App, nor in the results of the allocateIpAddress mutation, am I able to get the shared_v4 IP address of my app. In other words, it appears the App resolver is not returning shared_v4 addresses. I know it succeeds because the shared_v4 address shows up in the dashboard.

v6 IP addresses are returned as expected. null is returned when allocating a shared_v4 address, but for v6 addresses, the IpAddress Node is correctly returned.

In addition, when querying like below, graphql returns the error shown. This isn’t a problem for the ipv6 address:

app(name: $name) {
    ipAddress(address: "66.241.125.136") {
      region
      address
    }
    ...
}
// returned error:
  "errors": [
    {
      "message": "Could not find IPAssignment",
      "locations": [
        {
          "line": 3,
          "column": 5
        }
      ],
      "path": [
        "app",
        "ipAddress"
      ],
      "extensions": {
        "code": "NOT_FOUND"
      }
    }
  ]

This appears to be a bug!

2

There’s a sharedIpAddress field on the App type:

query {
  app(name: $appName) {
    sharedIpAddress
  }
}
3

Of course! But why not include it in the ipAddresses array when that supports identifying the type?

4

I think it’s just something we haven’t managed to get round to unifying! We don’t offer shared ipv6 (because dedicated ipv6 is free), so sharedIpAddress is always going to be a shared ipv4, if that helps!

5

Thank you for the insight! Cheers.

1 Like
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.