Topics
Supporting creating OAuth access tokens for other users.
- Add the
for_useroption to theherve4m.quay.quay_api_tokenmodule. With this option you can assign OAuth API tokens to other users (Quay 3.12 and later).
Adding the repo_image_expiry event to the herve4m.quay.quay_notification module.
- herve4m.quay.quay_notification - New
repo_image_expiryevent and newimage_expiry_daysparameter (Quay 3.12)
Testing against Quay v3.12.0.
- herve4m.quay.quay_api_token - remove from the parameter group, because the options are different for this module.
- herve4m.quay.quay_api_token - update the documentation to indicate that the user must have admin rights to the organization.
- herve4m.quay.quay_docker_config - Build a Docker configuration in JSON format
- Add support for the auto-pruning tags feature in Quay 3.11 for organizations and repositories. The
herve4m.quay.quay_organizationandherve4m.quay.quay_repositorymodules now have theauto_prune_methodandauto_prune_valueoptions.
- herve4m.quay.quay_team_oidc - Synchronize Quay Container Registry teams with OIDC groups
- herve4m.quay.quay_proxy_cache - Manage Quay Container Registry proxy cache configurations
Testing against Quay version 3.10.1.
Testing against Quay version 3.9.1.
Testing against Quay version 3.8.6.
- quay_user - Workaround empty SUPER_USERS configuration parameter. (#26)
Testing against Quay version 3.8.5.
- quay_api_token - Convert response headers in lowercase. (#23)
Testing against Quay version 3.8.0.
Adding the herve4m.quay.quay module defaults group.
- Add the
herve4m.quay.quaymodule defaults group. To avoid repeating common parameters, such asquay_hostorquay_token, in each task, you can define these common module parameters at the top of your play, in themodule_defaultssection, under thegroup/herve4m.quay.quaysubsection.
Updating documentation and testing against version 3.7.2
- In addition to token authentication, the modules can now connect to the Quay API by using a login and password scheme. The new
quay_usernameandquay_passwordparameters are mutually exclusive with thequay_tokenparameter.
Collection tested against Red Hat Quay v3.7.0
- herve4m.quay.quay_org - Create and configure a Red Hat Quay organization
- herve4m.quay.quay_api_token - Create OAuth access tokens for accessing the Red Hat Quay API
- herve4m.quay.quay_docker_token - Manage tokens for accessing Red Hat Quay repositories
- herve4m.quay.quay_manifest_label - Manage Red Hat Quay image manifest labels
- herve4m.quay.quay_manifest_label_info - Gather information about manifest labels in Red Hat Quay
- herve4m.quay.quay_team_ldap - Synchronize Red Hat Quay teams with LDAP groups
- Tests - add integration tests.
- quay_notification - add a check to verify that the repository exists.
New quay_first_user module
- herve4m.quay.quay_first_user - Create the first user account
- quay_notification - add the
vulnerability_levelparameter.
Collection tested against Red Hat Quay v3.6.1
New quay_repository_mirror module
New quay_vulnerability_info information module
Fix wrong project URLs
Initial public release.
- herve4m.quay.quay_application - Manage Red Hat Quay organizations
- herve4m.quay.quay_default_perm - Manage Red Hat Quay default repository permissions
- herve4m.quay.quay_image_info - Gather information about images in a Red Hat Quay repository
- herve4m.quay.quay_message - Manage Red Hat Quay global messages
- herve4m.quay.quay_notification - Manage Red Hat Quay repository notifications
- herve4m.quay.quay_organization - Manage Red Hat Quay organizations
- herve4m.quay.quay_repository - Manage Red Hat Quay repositories
- herve4m.quay.quay_robot - Manage Red Hat Quay robot accounts
- herve4m.quay.quay_tag_info - Gather information about tags in a Red Hat Quay repository
- herve4m.quay.quay_team - Manage Red Hat Quay teams
- herve4m.quay.quay_user - Manage Red Hat Quay users