-
Notifications
You must be signed in to change notification settings - Fork 75
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
Add docs for new API endpoints #3057
Conversation
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.
Just a few nits :)
docs/references/api.rst
Outdated
- Introduced in Ubuntu Pro Client Version: ``32~`` | ||
- Args: | ||
|
||
- ``token``: The token associated with a Pro subscriptionn |
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.
- ``token``: The token associated with a Pro subscriptionn | |
- ``token``: The token associated with a Pro subscription |
docs/references/api.rst
Outdated
- The services enabled during the attach operation | ||
* - ``reboot_required`` | ||
- *bool* | ||
- If the system requires a reboot after the attach operation |
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.
Presumably this is True if the system requires a reboot?
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, I will make it more explicit
docs/references/api.rst
Outdated
|
||
pro api u.pro.attach.token.full_token_attach.v1 | ||
|
||
Note that we don't need to explicit pass the token when calling the CLI command. |
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.
Note that we don't need to explicit pass the token when calling the CLI command. | |
Note that we don't need to explicitly pass the token when calling the CLI command. |
docs/references/api.rst
Outdated
pro api u.pro.attach.token.full_token_attach.v1 | ||
|
||
Note that we don't need to explicit pass the token when calling the CLI command. | ||
If we define a json file (i.e. file.json) with the same attributes as the options for this endpoint: |
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.
If we define a json file (i.e. file.json) with the same attributes as the options for this endpoint: | |
If we define a JSON file (i.e. ``file.json``) with the same attributes as the options for this endpoint: |
docs/references/api.rst
Outdated
"auto_enable_services": false | ||
} | ||
|
||
Then, we can call the API like this: |
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.
Then, we can call the API like this: | |
Then we can call the API like this: |
docs/references/api.rst
Outdated
- The services disabled during the detach operation | ||
* - ``reboot_required`` | ||
- *bool* | ||
- If the system requires a reboot after the detach operation |
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.
Should this also be "True if..."
docs/references/api.rst
Outdated
.. tab-item:: Explanation | ||
:sync: explanation | ||
|
||
The *contract_status* field can return 4 different states, they are: |
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.
The *contract_status* field can return 4 different states, they are: | |
The ``contract_status`` field can return 4 different states, they are: |
docs/references/api.rst
Outdated
* **grace-period**: The contract is in the grace period. This means that it is expired, | ||
there are still some days were the contract will be valid. |
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.
* **grace-period**: The contract is in the grace period. This means that it is expired, | |
there are still some days were the contract will be valid. | |
* **grace-period**: The contract is in the grace period. This means that it is expired, | |
but there are still some days where the contract will be valid. |
fca8e6e
to
327a992
Compare
@s-makin updated |
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.
Just two little nits
docs/references/api.rst
Outdated
- The services enabled during the attach operation | ||
* - ``reboot_required`` | ||
- *bool* | ||
- True If the system requires a reboot after the attach operation |
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.
- True If the system requires a reboot after the attach operation | |
- True if the system requires a reboot after the attach operation |
docs/references/api.rst
Outdated
* - ``contract_status`` | ||
- *str* | ||
- The current contract status (active, grace-period, active-soon-to-expire, expired). | ||
Please refer to the explanation tab for a description of each state |
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.
Please refer to the explanation tab for a description of each state | |
Please refer to the explanation tab for a description of each state. |
327a992
to
1aaef91
Compare
@s-makin fixed |
Why is this needed?
Add documentation for the following API related changes:
Test Steps
Verify if the documentation page is correctly rendered and we are not missing any information related to the API changes
Checklist
Does this PR require extra reviews?