-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix tagging in documentation strings (#10)
- Loading branch information
Showing
26 changed files
with
305 additions
and
292 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
#!/usr/bin/python | ||
# -*- coding: utf-8 -*- | ||
|
||
# Copyright: (c) 2021, 2022 Hervé Quatremain <[email protected]> | ||
# Copyright: (c) 2021, 2022, 2024 Hervé Quatremain <[email protected]> | ||
# GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt) | ||
|
||
# For accessing the API documentation from a running system, use the swagger-ui | ||
|
@@ -48,7 +48,7 @@ | |
type: str | ||
type: | ||
description: | ||
- Type of the account defined in I(name). Choose C(user) | ||
- Type of the account defined in O(name). Choose V(user) | ||
for both user and robot accounts. | ||
type: str | ||
choices: [user, team] | ||
|
@@ -57,33 +57,33 @@ | |
description: | ||
- Permission that Quay automatically grants to the user or team on new | ||
created repositories in the organization. | ||
- If you do not provide that parameter, then the module uses C(read) by | ||
- If you do not provide that parameter, then the module uses V(read) by | ||
default. | ||
type: str | ||
choices: [read, write, admin] | ||
creator: | ||
description: | ||
- Quay applies the default permission only when repositories are created | ||
by the user that you define in I(creator). | ||
- By default, if you do not provide that I(creator) parameter, then Quay | ||
by the user that you define in O(creator). | ||
- By default, if you do not provide that O(creator) parameter, then Quay | ||
applies the default permission to all new repositories, whoever creates | ||
them. | ||
- You cannot use robot accounts or teams for the I(creator) parameter. | ||
- You cannot use robot accounts or teams for the O(creator) parameter. | ||
You can only use regular user accounts. | ||
type: str | ||
state: | ||
description: | ||
- If C(absent), then the module deletes the default permission. | ||
- If C(present), then the module creates the default permission if it | ||
- If V(absent), then the module deletes the default permission. | ||
- If V(present), then the module creates the default permission if it | ||
does not already exist. | ||
- If the default permission already exists, then the module updates its | ||
role parameter (C(read), C(write), or C(admin)). | ||
role parameter (V(read), V(write), or V(admin)). | ||
type: str | ||
default: present | ||
choices: [absent, present] | ||
notes: | ||
- Supports C(check_mode). | ||
- The token that you provide in I(quay_token) must have the "Administer | ||
- The token that you provide in O(quay_token) must have the "Administer | ||
Organization" and "Administer User" permissions. | ||
extends_documentation_fragment: | ||
- infra.quay_configuration.auth | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
#!/usr/bin/python | ||
# -*- coding: utf-8 -*- | ||
|
||
# Copyright: (c) 2021, 2022 Hervé Quatremain <[email protected]> | ||
# Copyright: (c) 2021, 2022, 2024 Hervé Quatremain <[email protected]> | ||
# GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt) | ||
|
||
# For accessing the API documentation from a running system, use the swagger-ui | ||
|
@@ -46,16 +46,16 @@ | |
- You probably want that user account to have superuser permissions so | ||
that you can use the returned token to create additional objects. | ||
To do so, add the account name to the C(SUPER_USERS) section in the | ||
C(config.yaml) file before using the M(infra.quay_configuration.quay_first_user) | ||
module. | ||
C(config.yaml) file before using the | ||
M(infra.quay_configuration.quay_first_user) module. | ||
required: true | ||
type: str | ||
email: | ||
description: | ||
- User's email address. | ||
- If your Quay administrator has enabled the mailing capability of your | ||
Quay installation (C(FEATURE_MAILING) to C(true) in C(config.yaml)), | ||
then this I(email) parameter is mandatory. | ||
then this O(email) parameter is mandatory. | ||
type: str | ||
password: | ||
description: | ||
|
@@ -66,12 +66,12 @@ | |
type: str | ||
create_token: | ||
description: | ||
- If C(yes), then an OAuth access token is created and returned. You can | ||
- If V(true), then an OAuth access token is created and returned. You can | ||
use that returned token with the other Quay modules, by setting it in | ||
the I(quay_token) parameter. The token is valid for 2 hours 30 minutes. | ||
- If C(no), then no access token is created. | ||
the C(quay_token) parameter. The token is valid for 2 hours 30 minutes. | ||
- If V(false), then no access token is created. | ||
type: bool | ||
default: no | ||
default: false | ||
notes: | ||
- The module requires Quay version 3.6 or later. | ||
- To use the module, you must enable the first user creation feature of your | ||
|
@@ -104,7 +104,7 @@ | |
description: | ||
- The access token that you can use for subsequent module calls. | ||
- The token is valid for 2 hours 30 minutes. | ||
returned: only when you set the I(create_token) parameter to C(yes) | ||
returned: only when you set the O(create_token) parameter to V(true) | ||
type: str | ||
sample: W2YX0V838JZ5FHHUH82Q25FZZMRX8YTB1MTN56P3 | ||
email: | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.