Mirrors/ansible-collection-hetzner-hcloud
2
0
Fork 0
mirror of https://github.com/ansible-collections/hetzner.hcloud synced 2024-09-20 06:22:11 +00:00
Code Issues Projects Releases Packages Wiki Activity
No description
115 commits 6 branches 46 tags 2.7 MiB
Python 97.7%
Shell 2.1%
Makefile 0.2%
Find a file
Julian Tölle bfe0f7a575
feat(inventory): handle servers that dont work with connect_with setting (#187) 
Currently if any of the servers in the inventory do not work with the
selected `connect_with` mode, the script exits and returns 0 servers.
This can happen for example if one of your servers does not have a public
ipv4 address, but you set `connect_with: public_ipv4` (default).

This commit changes the behaviour to log a warning message, and just skip
setting `ansible_host` for this server. This server will not be reachable
by ansible by default, but users can use `compose` to override the
`ansible_host` that we set based on the other variables.
2023-02-01 10:41:36 +01:00
.azure-pipelines Add ansible 2.15 tests (#154) 2022-09-27 05:57:31 +02:00
.github/workflows Antisibul (#151) 2022-09-14 10:15:22 +02:00
changelogs feat(inventory): handle servers that dont work with connect_with setting (#187) 2023-02-01 10:41:36 +01:00
meta Polish old modules and collection for release (#11) 2020-06-29 13:53:01 +02:00
plugins feat(inventory): handle servers that dont work with connect_with setting (#187) 2023-02-01 10:41:36 +01:00
tests Add possibility to specify private network when creating or updating servers (#160) 2022-11-09 22:31:03 +01:00
.gitignore Implement Firewall Support (#63) 2021-03-11 11:07:41 +01:00
.gitlab-ci.yml Add managed certs support (#72) 2021-04-06 11:59:59 +02:00
CHANGELOG.rst chore: prepare v1.9.1 (#177) 2022-12-21 10:21:42 +01:00
COPYING Initial commit 2020-03-09 13:36:01 +00:00
galaxy.yml chore: prepare v1.9.1 (#177) 2022-12-21 10:21:42 +01:00
README.md Prepare Release 1.7.0 2022-06-09 14:51:49 +02:00

README.md

Build Status Codecov

Ansible Collection: hetzner.hcloud

Ansible Hetzner Cloud Collection for controlling your Hetzner Cloud Resources.

Release notes

See here.

Documentation

The documentation for all modules are available through ansible-doc.

Sample: ansible-doc hetzner.hcloud.hcloud_server shows the documentation for the hcloud_server module.

For all modules that were part of Ansible directly (before Ansible 2.11) we also have the documentation published in the Ansible documentation: https://docs.ansible.com/ansible/latest/collections/hetzner/hcloud/

Development

Requirements

You should place the collection (clone the repository) into the Ansible collection path. Normally this is ~/.ansible/collections/ansible_collections/<namespace>/<collection, so for our collection it would be: ~/.ansible/collections/ansible_collections/hetzner/hcloud.

git clone git@github.com:ansible-collections/hetzner.hcloud.git ~/.ansible/collections/ansible_collections/hetzner/hcloud

After this you just need ansible installed.

Testing

Testing is done via ansible-test. Make sure to have a cloud-config-hcloud.ini file in tests/integration which contains the hcloud API token:

[default]
hcloud_api_token=<token>

After this you should be able to use ansible-test integration to perform the integration tests for a specific module. Sample:

ansible-test integration --color --local  -vvv hcloud_server // Executed all integration tests for hcloud_server module

Releasing a new version

Generating changelog from fragments

  1. Check if the changelog fragments are available (there should be files in changelogs/fragments)
  2. Run antsibull-changelog release --version <version>, it should remove all fragments and change the changelogs/changlog.yaml and CHANGELOG.rst
  3. Push the changes to the main branch
  4. Tag the release through the Github UI, after this the Github Actions will run and publish the collection to Ansible Galaxy