33782fecd5
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [ansible-community/antsibull-changelog](https://redirect.github.com/ansible-community/antsibull-changelog) | repository | minor | `0.31.2` -> `0.32.0` | Note: The `pre-commit` manager in Renovate is not supported by the `pre-commit` maintainers or community. Please do not report any problems there, instead [create a Discussion in the Renovate repository](https://redirect.github.com/renovatebot/renovate/discussions/new) if you have any questions. --- ### Release Notes <details> <summary>ansible-community/antsibull-changelog (ansible-community/antsibull-changelog)</summary> ### [`v0.32.0`](https://redirect.github.com/ansible-community/antsibull-changelog/releases/tag/0.32.0) [Compare Source](https://redirect.github.com/ansible-community/antsibull-changelog/compare/0.31.2...0.32.0) ##### Release Summary Feature release. ##### Major Changes - The new configuration setting <code>output</code> allows to configure more precisely which changelog files are generated and how they are formatted ([#​190](https://redirect.github.com/ansible-community/antsibull-changelog/issues/190), [#​194](https://redirect.github.com/ansible-community/antsibull-changelog/pull/194)). ##### Minor Changes - Antsibull-changelog now depends on Pydantic 2 ([#​193](https://redirect.github.com/ansible-community/antsibull-changelog/pull/193)). - Antsibull-changelog now uses Pydantic to parse and validate the config. This means that validation is more strict than before and might reject configs that were incorrect, but still got accepted somehow ([#​193](https://redirect.github.com/ansible-community/antsibull-changelog/pull/193)). ##### Breaking Changes / Porting Guide - When using antsibull-changelog as a library, <code>ChangelogConfig</code>'s constructor should no longer be called directly. Instead, use the class method <code>ChangelogConfig.parse()</code>, which has the same signature than the previous constructor, except that <code>ignore_is_other_project</code> now must be a keyword parameter ([#​193](https://redirect.github.com/ansible-community/antsibull-changelog/pull/193)). - When using antsibull-changelog as a library, <code>rendering.changelog.generate_changelog()</code> now needs a <code>ChangelogOutput</code> object instead of the <code>document_format: TextFormat</code> parameter, and the <code>config</code> and <code>changelog_path</code> parameters have been removed ([#​194](https://redirect.github.com/ansible-community/antsibull-changelog/pull/194)). - When using the <code>--output</code> argument for <code>antsibull-changelog generate</code>, the generated changelog's title will not contain any parts of the version number. If you need this, [please create an issue](https://redirect.github.com/ansible-community/antsibull-changelog/issues/new) ([#​194](https://redirect.github.com/ansible-community/antsibull-changelog/pull/194)). ##### Deprecated Features - The configuration settings <code>changelog_filename_template</code>, <code>changelog_filename_version_depth</code>, and <code>output_formats</code> are deprecated and will eventually be removed. Use the new setting <code>output</code> instead. Note that there are no runtime warnings right now. If the time to remove them comes nearer, there will be runtime warnings for a longer time first before they are actually removed ([#​194](https://redirect.github.com/ansible-community/antsibull-changelog/pull/194)). ##### Removed Features (previously deprecated) - Python API: remove <code>antsibull_changelog.rst</code> module ([#​183](https://redirect.github.com/ansible-community/antsibull-changelog/pull/183)). - Python API: remove constructor arguments <code>plugins</code> and <code>fragments</code> from class <code>ChangelogGenerator</code> in <code>antsibull_changelog.rendering.changelog</code> ([#​183](https://redirect.github.com/ansible-community/antsibull-changelog/pull/183)). - Python API: remove method <code>ChangelogEntry.add_section_content</code>, class <code>ChangelogGenerator</code>, and function <code>generate_changelog</code> from <code>antsibull_changelog.changelog_generator</code> ([#​183](https://redirect.github.com/ansible-community/antsibull-changelog/pull/183)). - When using antsibull-changelog as a library, the fields <code>changelog_filename_template</code>, <code>changelog_filename_version_depth</code>, and <code>output_formats</code> are no longer available in <code>ChangelogConfig</code>. Use <code>output</code> instead ([#​194](https://redirect.github.com/ansible-community/antsibull-changelog/pull/194)). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/ansible-collections/hetzner.hcloud). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xOTQuMSIsInVwZGF0ZWRJblZlciI6IjM5LjE5NC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
|---|---|---|
| .azure-pipelines | ||
| .github | ||
| changelogs | ||
| docs/docsite | ||
| examples | ||
| meta | ||
| plugins | ||
| scripts | ||
| tests | ||
| .ansible-lint | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .pre-commit-config.yaml | ||
| CHANGELOG.rst | ||
| COPYING | ||
| galaxy.yml | ||
| Makefile | ||
| pyproject.toml | ||
| README.md | ||
| renovate.json | ||
| requirements.txt | ||
Ansible Collection: hetzner.hcloud
Ansible Hetzner Cloud Collection for controlling your Hetzner Cloud Resources.
Communication
-
Join the Ansible forum:
- Get Help: get help or help others.
- Posts tagged with 'hcloud': subscribe to participate in collection-related conversations.
- Social Spaces: gather and interact with fellow enthusiasts.
- News & Announcements: track project-wide announcements including social events.
-
The Ansible Bullhorn newsletter: used to announce releases and important changes.
For more information about communication, see the Ansible communication guide.
Python version compatibility
This collection depends on the hcloud library. Due to the hcloud Python Support Policy this collection requires Python 3.8 or greater.
Release notes
See here.
Release policy
The main branch is used for the development of the latest versions of the collections, and may contain breaking changes. The stable-* branches (e.g. stable-1 for the 1.x.y releases) are used to cut additional minor or patch releases if needed, but we do not provide official support for multiple versions of the collection.
Documentation
The documentation for all modules are available through ansible-doc.
Sample: ansible-doc hetzner.hcloud.server shows the documentation for the 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 hetzner.hcloud.server // Executed all integration tests for server module
Releasing a new version
If there are releasable changes, release-please will open a PR on GitHub with the proposed version. When this PR is merged, release-please will tag the release.