Releases: linux-system-roles/cockpit
Version 1.4.4
Version 1.4.3
[1.4.3] - 2023-01-20
New Features
- none
Bug Fixes
- ansible-lint 6.x fixes
Other Changes
- Add check for non-inclusive language
- cleanup non-inclusive words.
Version 1.4.2
[1.4.2] - 2022-11-21
New Features
- none
Bug Fixes
- ansible-core 2.14 support - remove another warn
Other Changes
- use fedora.linux_system_roles.certificate role in tests
The dependencies will be installed everywhere, so just use them
in the tests
Version 1.4.1
[1.4.1] - 2022-11-15
New Features
- none
Bug Fixes
- make role work with ansible-core 2.14 - fix ansible-lint 6.x issues (#81)
Other Changes
- none
Version 1.4.0
[1.4.0] - 2022-11-01
New Features
- Use the firewall role and the selinux role from the cockpit role (#76)
Since cockpit_port is a public api of the cockpit role, define it
in defaults/main.yml as null.
-
Introduce cockpit_manage_firewall to use the firewall role to
manage the cockpit service.
Default to false - means the firewall role is not used. -
Add the test check task tasks/check_port.yml for verifying the
ports status. -
Add meta/collection-requirements.yml.
-
Introduce cockpit_manage_selinux to use the selinux role to
manage the ports in the cockpit service.
Assign websm_port_t to the cockpit service ports.
Default to false - means the selinux role is not used. -
Use the certificate role to create the cert and the key (#78)
-
Introduce a variable cockpit_certificates to set the certificate_requests.
-
Update README so that using the certificate role is recommended.
Add a check and README note for not supporting creating a self-signed
certificate on RHEL/CentOS-7.
Bug Fixes
- none
Other Changes
- workflows: Add integration-tests for Ubuntu 22.04 (#68)
The current LTS 22.04 is the more interesting target. This detects bugs
like [1]. Keep 20.04 running as well for the time being.
[1] linux-system-roles/certificate#130
- Clone the certificate role in the temporary dir. (#77)
Version 1.3.0
[1.3.0] - 2022-07-29
New Features
- Add customization of port (#67)
Introduce a cockpit_port
variable which changes the default port 9090,
as per https://cockpit-project.org/guide/latest/listen.html#listen-systemd
This requires an extra step with SELinux: It only allows cockpit to own port
9090, so for any other port the user needs to adjust the policy first. As this
is outside of what the cockpit role ought to mess with, only document it and do
that in the tests.
Fixes #63
Bug Fixes
- none
Other Changes
-
changelog_to_tag action - support other than "master" for the main branch name (#66)
-
fix yamllint indentation issue
Version 1.2.5
bump tox-lsr version to 2.11.0; remove py37; add py310 (#59)
[citest skip] bump tox-lsr version to 2.11.0; remove py37; add py310 (#59)
tox-lsr version 2.11.0 has support for collection-requirements.yml,
runqemu improvements, and support for python 3.10
python 3.7 is not used on any supported platform, so remove it
Signed-off-by: Rich Megginson rmeggins@redhat.com
support gather_facts: false; support setup-snapshot.yml (#58)
Test "cockpit_packages: full" scenario
This has bug reports such as [1], ensure that this generally works
everywhere.
[1] #51
support gather_facts: false; support setup-snapshot.yml (#58)
- support gather_facts: false
Some users use gather_facts: false
in their playbooks. This changes
the role to work in that case, by gathering only the facts it requires
to run.
-
add .tox/ to .gitignore
-
must use public: true to export role private variables
must also include the certificate role in the same play to use the
role variables exported by the certificate role
- add setup-snapshot.yml for CI test image preparation
CI testing can be sped up by creating a snapshot image pre-installed
with packages. tests/setup-snapshot.yml can be used by a CI system
to do this.
drop obsolete and testing packages
Skip cockpit-tests everywhere
cockpit-tests is not in the base/extra composes in RHEL 7, and should
not be. It's only being used during gating testing.
Drop obsolete packages from README
-docker and -ostree are only a thing on RHEL/CentOS 7, most OSes have
them in the exclude list. In particular, you would never find -podman
and -docker on the same OS.
-tests should not ever be installed automatically.
This should reduce confusion.