The role used .yaml while the molecule scenario used .yml, because molecule hard codes molecule.yml and has no fallback for the other extension. Aligning all files on .yml keeps the extension consistent across the repository and avoids surprises when a tool only supports one of both spellings. Co-authored-by: Copilot <copilot@github.com>
27 lines
483 B
YAML
27 lines
483 B
YAML
dependencies: []
|
|
galaxy_info:
|
|
author: "Markus Pesch"
|
|
company: "Cryptic Systems"
|
|
description: "Role to create and manage an existing PKI infrastructure"
|
|
galaxy_tags:
|
|
- ca
|
|
- ssl
|
|
- tls
|
|
license: "MIT"
|
|
min_ansible_version: "2.9"
|
|
namespace: volker-raschek
|
|
platforms:
|
|
- name: ArchLinux
|
|
versions:
|
|
- all
|
|
- name: EL
|
|
versions:
|
|
- all
|
|
- name: Fedora
|
|
versions:
|
|
- all
|
|
- name: Ubuntu
|
|
versions:
|
|
- all
|
|
role_name: "certificate_authority"
|