toolshed/alakazam
2
1
Fork 3
Code Issues 4 Pull Requests 1 Packages Projects Releases Wiki Activity

feat: add config-sets support #8

Open
dannygroenewegen wants to merge 1 commits from eCommons/alakazam:config-sets into main
pull from: eCommons/alakazam:config-sets
merge into: toolshed:main
Conversation 0 Commits 1 Files Changed 2 +95 -21
dannygroenewegen commented 2026-05-28 10:05:33 +00:00
Contributor
Copy Link

Adds support for a config-sets.yml file at the root path where named bundles
of app configurations (env, hooks, secrets) can be defined and activated
per-instance or per-group, eliminating duplication across instance configs.

  • Config-sets are defined as top-level keys in config-sets.yml
  • Activate a set in any instance or group alaka.yml with CONFIG-SETS: : true
  • Disable a set inherited from a group with CONFIG-SETS: : false
  • Merge priority: group < config-set < instance
  • Warns when a config-set is enabled but not defined in config-sets.yml
  • Warns when a config-set targets an app not listed in the instance config
  • Adds examples/config-sets.yml with bbb and calendar config-set examples

See #3

Adds support for a config-sets.yml file at the root path where named bundles of app configurations (env, hooks, secrets) can be defined and activated per-instance or per-group, eliminating duplication across instance configs. - Config-sets are defined as top-level keys in config-sets.yml - Activate a set in any instance or group alaka.yml with CONFIG-SETS: <name>: true - Disable a set inherited from a group with CONFIG-SETS: <name>: false - Merge priority: group < config-set < instance - Warns when a config-set is enabled but not defined in config-sets.yml - Warns when a config-set targets an app not listed in the instance config - Adds examples/config-sets.yml with bbb and calendar config-set examples See #3
dannygroenewegen added 1 commit 2026-05-28 10:05:33 +00:00
feat: add config-sets support d2473ca74a 
Adds support for a config-sets.yml file at the root path where named bundles
of app configurations (env, hooks, secrets) can be defined and activated
per-instance or per-group, eliminating duplication across instance configs.

- Config-sets are defined as top-level keys in config-sets.yml
- Activate a set in any instance or group alaka.yml with CONFIG-SETS: <name>: true
- Disable a set inherited from a group with CONFIG-SETS: <name>: false
- Merge priority: group < config-set < instance
- Warns when a config-set is enabled but not defined in config-sets.yml
- Warns when a config-set targets an app not listed in the instance config
- Adds examples/config-sets.yml with bbb and calendar config-set examples
dannygroenewegen requested review from moritz 2026-05-28 10:05:49 +00:00
dannygroenewegen requested review from simon 2026-05-28 10:05:59 +00:00
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u config-sets:eCommons-config-sets
git checkout eCommons-config-sets
Sign in to join this conversation.
Reviewers
No Reviewers
moritz
simon
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 amras Apfelwurm BornDeleuze carla cas coopcloud cyrnel decentral1se dede fauno iexos jade jjsfunhouse jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie moosemower moritz notplants oxaliq p4u1 pharaohgraphy renovate-bot ripclap simon sixsmith stevensting trav val yksflip
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/alakazam#8
No description provided.
Delete Branch "eCommons/alakazam:config-sets"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?