Skip to content

Conversation

Dorthu
Copy link
Collaborator

@Dorthu Dorthu commented Aug 31, 2020

Closes linode/linode-cli#207

It was reported above that the CLI wasn't showing complete output for
IPv6 Ranges compared to IPv6 Pools. Turns out this is because the docs
were missing several fields for ranges.

This PR adds the missing fields to IPv6Ranges. I based the descriptions
and values off of the equivalent fields in IPv6Pool.

Closes linode/linode-cli#207

It was reported above that the CLI wasn't showing complete output for
IPv6 Ranges compared to IPv6 Pools.  Turns out this is because the docs
were missing several fields for ranges.

This PR adds the missing fields to IPv6Ranges.  I based the descriptions
and values off of the equivalent fields in IPv6Pool.
@Dorthu Dorthu requested a review from leslitagordita August 31, 2020 12:02
Made all example v6 addresses valid and correct where they're used.
@Dorthu Dorthu force-pushed the bugfix/fill-in-v6-range-object branch from 433de1d to 66b4019 Compare September 1, 2020 11:32
Copy link
Contributor

@leslitagordita leslitagordita left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Dorthu added some clarification to the List IPv6 Ranges endpoint re: /64 block for an IPv6 range and the requirement to open up a support ticket.

@Dorthu
Copy link
Collaborator Author

Dorthu commented Sep 8, 2020

Thank you! 👍

@leslitagordita leslitagordita merged commit 2992bbc into linode:development Sep 8, 2020
LBGarber pushed a commit to LBGarber/linode-api-docs that referenced this pull request Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

listing v6-ranges does not indicate prefix length

3 participants