• Germany & Cyberspace
  • Does infrastructure crimes with Nix and Ansible.

  • Joined on 2024-01-14
june commented on pull request CCCHH/ansible-infra#98 2026-08-02 02:05:42 +02:00
new z9 ccchh router

Some spacing seems to be off here.

june commented on pull request CCCHH/ansible-infra#98 2026-08-02 02:05:42 +02:00
new z9 ccchh router

Some spacing seems to be off here as well.

june commented on pull request CCCHH/ansible-infra#98 2026-08-02 02:05:42 +02:00
new z9 ccchh router

Same here with the resolver.

june commented on pull request CCCHH/ansible-infra#98 2026-08-02 02:05:42 +02:00
new z9 ccchh router

I'm not quite sure, if this is actually needed for resolving hostnames in the config. If everything works without the resolver config option, then lets just remove it.

june commented on pull request CCCHH/ansible-infra#98 2026-08-02 02:05:42 +02:00
new z9 ccchh router

If all tasks are in the block, then this doesn't need to be a block.

june commented on pull request CCCHH/ansible-infra#98 2026-08-02 02:05:42 +02:00
new z9 ccchh router

I would just get rid of all the commented out options, if we don't use them anyway (and instead maybe link to a full-fledged config example from the docs or something).

june commented on pull request CCCHH/ansible-infra#98 2026-08-02 02:05:42 +02:00
new z9 ccchh router

I would rather remove this check and have it just fail while running the Ansible playbook, rather than installing a broken Kea deployment.

june commented on pull request CCCHH/ansible-infra#98 2026-08-02 02:05:42 +02:00
new z9 ccchh router

Again, I think rather not having the checks makes more sense for our use case.

june commented on pull request CCCHH/ansible-infra#98 2026-08-02 02:05:42 +02:00
new z9 ccchh router

This option isn't documented in the README.

june commented on pull request CCCHH/ansible-infra#98 2026-08-02 02:05:42 +02:00
new z9 ccchh router

This option isn't documented in the README.

june commented on pull request CCCHH/ansible-infra#98 2026-08-02 02:05:42 +02:00
new z9 ccchh router

This option isn't documented in the README.

june suggested changes for CCCHH/ansible-infra#129 2026-07-29 13:10:56 +02:00
add dooris role for setup of dooris interaction on the node itself

Thanks for the changes, looks good! Just two notes.

june commented on pull request CCCHH/ansible-infra#129 2026-07-29 13:10:56 +02:00
add dooris role for setup of dooris interaction on the node itself

This should probably use dooris__hostname.

june commented on pull request CCCHH/ansible-infra#129 2026-07-29 13:10:56 +02:00
add dooris role for setup of dooris interaction on the node itself

Having those be hardcoded with all else being configurable is a bit awkward, so I think making these variables as well make sense.

june approved CCCHH/ansible-infra#112 2026-07-22 21:50:22 +02:00
alloy(role): pull in alloy role that works from fux

Nice, let's go!

june approved CCCHH/keycloak-attribute-endpoints-p...#30 2026-07-21 22:17:24 +02:00
default-to-user-email

Nice!

june commented on pull request CCCHH/keycloak-attribute-endpoints-p...#26 2026-07-21 21:45:08 +02:00
Add exporting individual attributes and a map endpoint

Let's have a comment here to note that we leave this name for backwards compatibility.