https://github.com/redhat-cop/cloud_provision_automation_collection
Cloud automation provision that includes working with rhv, satellite and idm. Also includes configuring provisioned systems
https://github.com/redhat-cop/cloud_provision_automation_collection
automation-cop
Last synced: 3 months ago
JSON representation
Cloud automation provision that includes working with rhv, satellite and idm. Also includes configuring provisioned systems
- Host: GitHub
- URL: https://github.com/redhat-cop/cloud_provision_automation_collection
- Owner: redhat-cop
- Created: 2020-06-17T02:31:03.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2020-08-24T18:33:58.000Z (almost 5 years ago)
- Last Synced: 2025-01-13T12:43:46.229Z (5 months ago)
- Topics: automation-cop
- Language: Python
- Homepage:
- Size: 40 KB
- Stars: 0
- Watchers: 29
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# cloud_provision_automation_collection

# Foo Collection
[](https://github.com/ansible-collections/REPONAMEHERE/actions) [](https://codecov.io/gh/ansible-collections/REPONAMEHERE)
This is a collection of roles for RHV Provision, Satellite and IDM registration and VM configuration.
## Release Process
This collection uses an auatomated GitHub workflow to publish releases to Ansible Galaxy. This workflow can be found in `.github/workflows/galaxy-release.yml`. It is dependent on `release.yml` and `galaxy.yml.j2`. See instructions below for usage.To publish a release to Galaxy:
1) An administrator of the repository must configure a secret in the settings containing the API key for the Galaxy namespace. The secret should be called `ANSIBLE_GALAXY_APIKEY`. This is a one time step.
2) To publish a release, click "releases" at the top of repository home page and "Draft a new release"
3) The "Tag version" should be in the form `v#.#.#`. A suffix may be added such as `-dev#` or `rc#` for pre-releases. These will still publish to Galaxy but will not be chosen when installing `latest`. The version must be explicitly stated when installing to use pre-releases.
4) Title the release, it is recommended to use the "Tag version"
5) Clicking "Publish release" will initiate the workflow. If there are no errors building the collection, it will be automatically published to galaxy as the version suppied for "Tag version"## Tested with Ansible
## External requirements
This collection depends on the awx.collection since it uses the modules there.
### Supported connections
## Included content
## Using this collection
See [Ansible Using collections](https://docs.ansible.com/ansible/latest/user_guide/collections_using.html) for more details.
## Contributing to this collection
## Release notes
## Roadmap
## More information
- [Ansible Collection overview](https://github.com/ansible-collections/overview)
- [Ansible User guide](https://docs.ansible.com/ansible/latest/user_guide/index.html)
- [Ansible Developer guide](https://docs.ansible.com/ansible/latest/dev_guide/index.html)
- [Ansible Community code of conduct](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html)## Licensing
GNU General Public License v3.0 or later.
See [LICENCE](https://www.gnu.org/licenses/gpl-3.0.txt) to see the full text.