-
Notifications
You must be signed in to change notification settings - Fork 56
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #218 from tribe29/devel
Release 0.15.0
- Loading branch information
Showing
30 changed files
with
354 additions
and
620 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
breaking_changes: | ||
- Agent role - Remove host attribute `tag_agent` from the defaults. | ||
Should not be a breaking change, but be aware of it. | ||
|
||
minor_changes: | ||
- Agent role - Respect the variable `checkmk_agent_host_name` when downloading host specific agents. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
# https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs-how-to | ||
|
||
major_changes: | ||
- The host module now uses `name` instead of `host_name`. The latter is retained as an alias but will be removed with a future release. | ||
- The folder module now uses `name` instead of `title`. The latter is retained as an alias until further notice. | ||
|
||
## Line Format | ||
|
||
# When writing a changelog entry, use the following format: | ||
|
||
# - scope - description starting with a uppercase letter and ending with a period at the very end. Multiple sentences are allowed. | ||
|
||
# The scope is usually a module or plugin name or group of modules or plugins, for example, lookup plugins. While module names can (and should) be mentioned directly (foo_module), plugin names should always be followed by the type (foo inventory plugin). | ||
|
||
# For changes that are not really scoped (for example, which affect a whole collection), use the following format: | ||
|
||
# - Description starting with an uppercase letter and ending with a dot at the very end. Multiple sentences are allowed. | ||
|
||
|
||
## Possible keys: | ||
|
||
# breaking_changes | ||
|
||
# Changes that break existing playbooks or roles. This includes any change to existing behavior that forces users to update tasks. Displayed in both the changelogs and the Porting Guides. | ||
# major_changes | ||
|
||
# Major changes to Ansible itself. Generally does not include module or plugin changes. Displayed in both the changelogs and the Porting Guides. | ||
# minor_changes | ||
|
||
# Minor changes to Ansible, modules, or plugins. This includes new features, new parameters added to modules, or behavior changes to existing parameters. | ||
# deprecated_features | ||
|
||
# Features that have been deprecated and are scheduled for removal in a future release. Displayed in both the changelogs and the Porting Guides. | ||
# removed_features | ||
|
||
# Features that were previously deprecated and are now removed. Displayed in both the changelogs and the Porting Guides. | ||
# security_fixes | ||
|
||
# Fixes that address CVEs or resolve security concerns. Include links to CVE information. | ||
# bugfixes | ||
|
||
# Fixes that resolve issues. | ||
# known_issues | ||
|
||
# Known issues that are currently not fixed or will not be fixed. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
# https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs-how-to | ||
|
||
minor_changes: | ||
- The playbooks shipped with the collection were cleaned up and update. Just for awareness. | ||
|
||
## Line Format | ||
|
||
# When writing a changelog entry, use the following format: | ||
|
||
# - scope - description starting with a uppercase letter and ending with a period at the very end. Multiple sentences are allowed. | ||
|
||
# The scope is usually a module or plugin name or group of modules or plugins, for example, lookup plugins. While module names can (and should) be mentioned directly (foo_module), plugin names should always be followed by the type (foo inventory plugin). | ||
|
||
# For changes that are not really scoped (for example, which affect a whole collection), use the following format: | ||
|
||
# - Description starting with an uppercase letter and ending with a dot at the very end. Multiple sentences are allowed. | ||
|
||
|
||
## Possible keys: | ||
|
||
# breaking_changes | ||
|
||
# Changes that break existing playbooks or roles. This includes any change to existing behavior that forces users to update tasks. Displayed in both the changelogs and the Porting Guides. | ||
# major_changes | ||
|
||
# Major changes to Ansible itself. Generally does not include module or plugin changes. Displayed in both the changelogs and the Porting Guides. | ||
# minor_changes | ||
|
||
# Minor changes to Ansible, modules, or plugins. This includes new features, new parameters added to modules, or behavior changes to existing parameters. | ||
# deprecated_features | ||
|
||
# Features that have been deprecated and are scheduled for removal in a future release. Displayed in both the changelogs and the Porting Guides. | ||
# removed_features | ||
|
||
# Features that were previously deprecated and are now removed. Displayed in both the changelogs and the Porting Guides. | ||
# security_fixes | ||
|
||
# Fixes that address CVEs or resolve security concerns. Include links to CVE information. | ||
# bugfixes | ||
|
||
# Fixes that resolve issues. | ||
# known_issues | ||
|
||
# Known issues that are currently not fixed or will not be fixed. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.