Skip to content

Feat/google chrome roles#249

Open
danyalberchtoldlf wants to merge 9 commits into
mainfrom
feat/google-chrome-roles
Open

Feat/google chrome roles#249
danyalberchtoldlf wants to merge 9 commits into
mainfrom
feat/google-chrome-roles

Conversation

@danyalberchtoldlf
Copy link
Copy Markdown
Contributor

No description provided.

Deploy /etc/icingaweb2/modules/pdfexport/config.ini so the module talks to
the chrome-headless service over the Chrome DevTools Protocol by default
(host/port), with an optional fall-back to a local Chrome binary. Move the
platform-variables import into an always-tagged block so the new
icingaweb2_module_pdfexport:configure tag can be run on its own. Wire the
repo_epel, repo_google_chrome and google_chrome roles into both the
standalone playbook and setup_icinga2_master.yml, with *__skip_* opt-outs
tracking the existing pdfexport skip flag.
…lean

Without bind_any the chrome-headless-proxy.socket cannot bind the listen
port on hosts where the port carries an unexpected SELinux port type
(on Rocky/RHEL 9 the default 9222 is registered as hplip_port_t).
Remove the comments and the chrome-headless-before-socket ordering that
only existed to handle the cut-over from a pre-existing, non-socket-
activated chrome service. With no such legacy unit in the wild, the
regular notify chain (daemon-reload, restart socket, restart chrome on
template change) is sufficient.
Declare the two user-facing variables (basic_auth_login as 'raw',
mirror_url as 'str'), matching the pattern repo_remi established.
Also sort entries in roles/google_chrome/{meta/argument_specs.yml,
defaults/main.yml} alphabetically per CONTRIBUTING.md.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant