galaxy.yml

### REQUIRED
# The namespace of the collection. This can be a company/brand/organization or product namespace under which all
# content lives. May only contain alphanumeric lowercase characters and underscores. Namespaces cannot start with
# underscores or numbers and cannot contain consecutive underscores
namespace: ibm_messaging

# The name of the collection. Has the same character restrictions as 'namespace'
name: ibmmq

# The version of the collection. Must be compatible with semantic versioning
version: 1.0.3

# The path to the Markdown (.md) readme file. This path is relative to the root of the collection
readme: README-GALAXY.md

# A list of the collection's content authors. Can be just the name or in the format 'Full Name <email> (url)
# @nicks:irc/im.site#channel'
authors:
  - James Page <James.Page@ibm.com>
  - Stewart Mclaughlin <StewartMcLaughlin@ibm.com>
  - Mariana Villar Pacheco <marianavillarp@ibm.com>
  - Bimsara Pilapitiya <Bimsara.Pilapitiya@ibm.com>
  - Mohammad Alatoum <Mohammad.Alatoum@ibm.com>


### OPTIONAL but strongly recommended
# A short summary description of the collection
description: A collection for automating the installation and configuration of IBM MQ using Ansible on Ubuntu, Redhat, Windows and IBM AIX machines. Our aim is to make MQ-Ansible extensible for other platforms and more detailed IBM MQ configuration.

# Either a single license or a list of licenses for content inside of a collection. Ansible Galaxy currently only
# accepts L(SPDX,https://spdx.org/licenses/) licenses. This key is mutually exclusive with 'license_file'
# license:
# - Apache-2.0

# The path to the license file for the collection. This path is relative to the root of the collection. This key is
# mutually exclusive with 'license'
license_file: 'LICENSE'

# A list of tags you want to associate with the collection for indexing/searching. A tag name has the same character
# requirements as 'namespace' and 'name'
tags: 
  - ibm
  - ibmmq
  - mq
  - queue
  - linux
  - aix
  - windows

# Collections that this collection requires to be installed for it to be usable. The key of the dict is the
# collection label 'namespace.name'. The value is a version range
# L(specifiers,https://python-semanticversion.readthedocs.io/en/latest/#requirement-specification). Multiple version
# range specifiers can be set and are separated by ','
dependencies: {}

# The URL of the originating SCM repository
repository: https://github.com/ibm-messaging/mq-ansible

# The URL to any online docs
documentation: https://github.com/ibm-messaging/mq-ansible/blob/main/README.md

# The URL to the homepage of the collection/project
homepage: https://github.com/ibm-messaging/mq-ansible

# The URL to the collection issue tracker
issues: https://github.com/ibm-messaging/mq-ansible/issues

# A list of file glob-like patterns used to filter any files or directories that should not be included in the build
# artifact. A pattern is matched from the relative path of the file or directory of the collection directory. This
# uses 'fnmatch' to match the files or directories. Some directories and files like 'galaxy.yml', '*.pyc', '*.retry',
# and '.git' are always filtered. Mutually exclusive with 'manifest'
build_ignore:
  - ansible.cfg
  - .gitignore
  - .github
  - .git
  - .cache
  - '*.tar.gz'
  - docs
  - collections
  - venv
  - .idea
  - meta/context

# A dict controlling use of manifest directives used in building the collection artifact. The key 'directives' is a
# list of MANIFEST.in style
# L(directives,https://packaging.python.org/en/latest/guides/using-manifest-in/#manifest-in-commands). The key
# 'omit_default_directives' is a boolean that controls whether the default directives are used. Mutually exclusive
# with 'build_ignore'
# manifest: null