Skip to content
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

docs: Add information about "duration" API parameter #32

Merged
merged 1 commit into from
Oct 13, 2023

Conversation

akrejcir
Copy link
Collaborator

What this PR does / why we need it:
Added more information about the duration parameter.

Release note:

None

@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Oct 11, 2023
@akrejcir
Copy link
Collaborator Author

/cc @0xFelix

@kubevirt-bot kubevirt-bot requested a review from 0xFelix October 11, 2023 14:08
Copy link

@jcanocan jcanocan left a comment

Choose a reason for hiding this comment

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

Nice job! Dropped some comments! Hope you find them useful.

@@ -10,7 +10,14 @@ Where `${VMI_NAMESPACE}` and `${VMI_NAME}` are the namespace
and name of a running VMI.

#### Parameters
- `duration` - Duration while the token is valid
- `duration` - Duration while the token is valid. If it is not specified, then the token will expire after 10 minutes.

Choose a reason for hiding this comment

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

Suggested change
- `duration` - Duration while the token is valid. If it is not specified, then the token will expire after 10 minutes.
- `duration` - Time in which the token is valid. If it is not specified, then the token will expire after 10 minutes.

Feel free to reword my suggestion. But in any case, I find a bit redundant to define "duration" starting with the word "duration".

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think that wording "Time in which" is unclear if it is a specific time moment, or a duration.

docs/api.md Outdated Show resolved Hide resolved
Copy link
Member

@0xFelix 0xFelix left a comment

Choose a reason for hiding this comment

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

/approve

@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 0xFelix

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 12, 2023
@akrejcir
Copy link
Collaborator Author

I will change one thing.
/hold

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 12, 2023
@akrejcir akrejcir force-pushed the duration-doc branch 2 times, most recently from 7a54b7b to 9a562bc Compare October 12, 2023 09:18
@akrejcir
Copy link
Collaborator Author

/unhold

@kubevirt-bot kubevirt-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 12, 2023
Added more information about the "duration" parameter.

Signed-off-by: Andrej Krejcir <akrejcir@redhat.com>
@0xFelix
Copy link
Member

0xFelix commented Oct 13, 2023

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Oct 13, 2023
@kubevirt-bot kubevirt-bot merged commit b6a4077 into kubevirt:main Oct 13, 2023
@akrejcir akrejcir deleted the duration-doc branch October 13, 2023 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants