-
Notifications
You must be signed in to change notification settings - Fork 22
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
Updating screenshots for 1.2 before release to see the coverage #5878
base: release-1.2
Are you sure you want to change the base?
Conversation
Lots of great changes 👍🏼 |
…ot-1-2' into bkr-udpate-screenshot-1-2
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.
Sounds good
- Add the tab with just GraphQL even tho it's the only option
@@ -208,7 +249,7 @@ mutation { | |||
|
|||
In the mutation we passed additional data to the allocated resource, in this case we passed a description attribute. This description attribute will be set on the IP address that was allocated. You can do this for any other attribute and relationship for the destination address type. | |||
|
|||
#### Idempotent allocation of an IP address | |||
:::success Idempotent allocation of an IP address |
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.
Title has been replaced by success box?
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.
yes, a title of level 4 was not present in the index. The success box makes it more visual.
mutation { | ||
IpamVLANCreate(data:{ | ||
name: {value: "My vlan"}, | ||
vlan_id: {from_pool: {id: "My number pool"}} # Here we could either put the ID or HFID |
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.
vlan_id: {from_pool: {id: "My number pool"}} # Here we could either put the ID or HFID | |
vlan_id: {from_pool: {id: "My VLAN ID Pool"}} # Here we could either put the ID or HFID |
Beyond that I'm not sure anymore if it shouldn't be something like {hfid:["My VLAN ID Pool"]}
, to be tested I believe
No description provided.