vars: fix using vars module with multiple machines #1891
No reviewers
Labels
No Label
backups
blog
bootstrapping
bug
changes-requested
cli
documentation
duplicate
enhancement
facts
help wanted
invalid
Inventory
low_prio
manager
modules
needs-review
networking
packaging
question
secrets
template
test
tooling
user-testing
vm
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: clan/clan-core#1891
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "kenji/clan-core:fix-vars-multiple-machines"
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?
This filters the secrets to only include the secrets managed under
per-machine
andshared
,otherwise new deployments will fail, when using the vars module for multiple machines:
This doesn't fix all the edge cases with this approach.
We get a similar error if we deploy shared vars that are not
encrypted for our machine key. This needs to be addressed when
implementing the shared vars functionality.
Fixes #1892
@ -17,0 +18,4 @@
vars:
builtins.elem vars.machine [
config.clan.core.machineName
"shared"
Not sure, if this is correct.
Are the shared variables also encrypted under
shared/machine
?Should I remove this for now?