Erich Blume
64a99071e3
New `forgejo_actions_secrets` role syncs repository-level Actions secrets from 1Password to Forgejo via the Forgejo API. This replaces the previous manual process of copying secrets from 1Password to Forgejo UI. Requires a one-time manual setup of a Forgejo PAT with write:repository scope, stored in 1Password as the `api-token` field. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
15 lines
549 B
YAML
15 lines
549 B
YAML
---
|
|
# Forgejo Actions Secrets role configuration
|
|
#
|
|
# This role syncs repository-level Actions secrets from 1Password to Forgejo
|
|
# via the Forgejo API.
|
|
|
|
forgejo_actions_secrets_api_url: "https://forge.ops.eblu.me/api/v1"
|
|
forgejo_actions_secrets_owner: eblume
|
|
forgejo_actions_secrets_repo: blumeops
|
|
|
|
# Secrets to sync: list of {name: "SECRET_NAME", value_var: "ansible_fact_name"}
|
|
# The value_var references an Ansible fact set in playbook pre_tasks
|
|
forgejo_actions_secrets_list:
|
|
- name: ARGOCD_AUTH_TOKEN
|
|
value_var: forgejo_secret_argocd_token
|