This collection enables configuration of services to work with Ploigos. These assets can be utilized by the Ploigos Software Factory Operator, or standalone.
Supported components appear below. See the playbooks
directory in this collection for usage notes and examples.
Some of the included roles use the devsecops-api command:
pip install devsecops-api
This role configures an instance of ArgoCD for use with Ploigos. After supplying the relevant properties to the playbook, invoke it with:
ansible-playbook playbooks/argocd.yml
This role configures an instance of Gitea for use with Ploigos. Use a playbook like this:
If you're running this locally, the role will print out a Gitea Access Token that you'll need to use later. Be sure to store this somewhere safe. After supplying the relevant properties to the playbook, invoke it with:
ansible-playbook playbooks/gitea.yml
This role configures an instance of Gitea for use with Ploigos. This requires a Gitea Access Token. After supplying the relevant properties to the playbook, invoke it with:
ansible-playbook playbooks/jenkins.yml
This role configures an instance of Nexus for use as an artifact repository with Ploigos. After supplying the relevant properties to the playbook, invoke it with:
ansible-playbook playbooks/nexus_artifacts.yml
This role configures an instance of Nexus for use as a container registry with Ploigos. After supplying the relevant properties to the playbook, invoke it with:
ansible-playbook playbooks/nexus_containers.yml
This role configures an instance of Red Hat Quay for use with Ploigos. After supplying the relevant properties to the playbook, invoke it with:
ansible-playbook playbooks/quay.yml
This role configures an instance of Sonarqube for use with Ploigos. After supplying the relevant properties to the playbook, invoke it with:
ansible-playbook playbooks/sonarqube.yml
This role configures an instance of Tekton for use with Ploigos. After supplying the relevant properties to the playbook, invoke it with:
ansible-playbook playbooks/tekton.yml