Drop the hard dependency on silvarion.databases

sysadmin commented

2026-10-06 19:10:33 +00:00

Contributor

silvarion.databases is used optionally (forgejo_db_internal/gitea_db_internal: true with mysql/postgres), already documented as conditional in this README's own "Dependencies" section -- but declaring it in galaxy.yml made ansible-galaxy resolve it unconditionally at install time, even for invocations (e.g. just the Actions-runner feature) that never touch it.

Confirmed live via silvarion.provision's own install pipeline: installing this collection for a leaf that only used silvarion.repos.forgejo's Actions-runner support failed outright.

Also drops the CI workaround this already needed for the same reason, and fixes the README's stale "Collection Dependencies" section (referenced a requirements.yml that doesn't exist in this repo).

Install silvarion.databases yourself first if you use the internal-database feature -- no longer pulled in automatically.

🤖 Generated with Claude Code

https://claude.ai/code/session_012icUrjv3vgHtovVpHUFjdp

silvarion.databases is used optionally (forgejo_db_internal/gitea_db_internal: true with mysql/postgres), already documented as conditional in this README's own "Dependencies" section -- but declaring it in galaxy.yml made ansible-galaxy resolve it unconditionally at install time, even for invocations (e.g. just the Actions-runner feature) that never touch it. Confirmed live via silvarion.provision's own install pipeline: installing this collection for a leaf that only used `silvarion.repos.forgejo`'s Actions-runner support failed outright. Also drops the CI workaround this already needed for the same reason, and fixes the README's stale "Collection Dependencies" section (referenced a requirements.yml that doesn't exist in this repo). Install silvarion.databases yourself first if you use the internal-database feature -- no longer pulled in automatically. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_012icUrjv3vgHtovVpHUFjdp

sysadmin added 1 commit

2026-10-06 19:10:33 +00:00

Drop the hard dependency on silvarion.databases

Ansible Lint / ansible-lint (pull_request) Successful in 33s

Details

b853c07d62

silvarion.databases is used optionally -- forgejo_db_internal/
gitea_db_internal: true with a mysql or postgres backend, already
documented in this README's own "Dependencies" section as conditional.
But declaring it in galaxy.yml made ansible-galaxy resolve it
unconditionally at install time, even for the common case (e.g. just the
Actions-runner feature) that never touches it.

Confirmed live via silvarion.provision's own install pipeline: installing
this collection for a leaf that only used silvarion.repos.forgejo for its
Actions-runner support failed outright, because galaxy.yml's dependency
has to be satisfied regardless of which features a given invocation
actually exercises.

Also drops the CI workaround this already needed for the same reason
(.forgejo/workflows/ansible-lint.yml had its own explicit
silvarion.databases git-install step, now unnecessary), and fixes the
README's stale "Collection Dependencies" section (referenced a
requirements.yml that doesn't exist in this repo).

Install silvarion.databases yourself first if you use the
internal-database feature -- it is no longer pulled in automatically.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012icUrjv3vgHtovVpHUFjdp

sysadmin merged commit 1e93b129fe into main

2026-10-06 19:18:52 +00:00

sysadmin referenced this pull request from a commit

2026-10-06 19:18:52 +00:00

Merge pull request 'Drop the hard dependency on silvarion.databases' (#9) from fix/optional-databases-dependency into main

Rows
Columns

Drop the hard dependency on silvarion.databases #9