buluma/Publish Ansible Collection to Galaxy

Builds and deploys a Collection to Ansible Galaxy

Trust Signals

name	description	required	default
api_key	Ansible Galaxy API key. This should be stored in a Secret on Github. See https://help.github.com/en/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-actions#creating-and-using-secrets-encrypted-variables.	yes	—
collection_dir	The directory in which the Ansible Collection is stored. This defaults to the project root.	no	./
build	You can now choose to build a collection without publishing, and vice versa. If you wish to disable building a collection, set this parameter to "false."	yes	true
publish	You can now choose to publish a collection without building (from a pre-built archive), and vice versa. If you wish to disable publishing a collection, set this parameter to "false."	yes	true
galaxy_version	Dynamically inject a semver-compatible version into your galaxy.yml file.	no	—
galaxy_config_file	DEPRECATED. A collection must have a galaxy.yml file that contains the necessary information to build a collection artifact. Defaults to "galaxy.yml" in the `collection_dir`, which is by default the project root. This parameter is deprecated as Ansible Galaxy requires the file to be named `galaxy.yml` and to exist in the root of your Collection. Use `collection_dir` to specify a non-root directory for your Collection.	no	galaxy.yml

no outputs