Document the naming convention for secrets/configs #680

New Issue

decentral1se · 2025-09-10T19:58:38Z

decentral1se commented

2025-09-10 19:58:38 +00:00

In unreleased abra, the following:

		compose.mariadb.yml
		Lines 41 to 45 in e83ae638eb
	
				configs:

				  my_tune:

				    name: ${STACK_NAME}_my_cnf_${MY_CNF_VERSION}

				    file: my-tune.cnf

				    template_driver: golang

will always show the following in the overview:

my_tune: ? (missing version)

because my_tune != my_cnf in the name.

See toolshed/abra#550 (comment) for a good hot take. We can just document this and keep moving. This might bite us is the short-term with some bug reports but we can just point to the docs and try to fix the recipe configs. /cc @3wordchant

In unreleased `abra`, the following: https://git.coopcloud.tech/coop-cloud/nextcloud/src/commit/e83ae638ebe9efacb3cfd21766cec2eb7c15207f/compose.mariadb.yml#L41-L45 will always show the following in the overview: ``` my_tune: ? (missing version) ``` because `my_tune` != `my_cnf` in the `name`. See https://git.coopcloud.tech/toolshed/abra/issues/550#issuecomment-26622 for a good hot take. We can just document this and keep moving. This might bite us is the short-term with some bug reports but we can just point to the docs and try to fix the recipe configs. /cc @3wordchant

👀 1

decentral1se added the

documentation

label 2025-09-10 19:58:38 +00:00

decentral1se referenced this issue from a commit

2025-11-04 14:08:17 +00:00

docs: document naming convention

decentral1se commented

2025-11-04 14:08:33 +00:00

43c9ed1e56

https://git.coopcloud.tech/toolshed/docs.coopcloud.tech/commit/43c9ed1e56f20e5f495be55368b2f14f16ef1948

decentral1se closed this issue