[Feature] Ability to exclude secrets from sync #1315

Open
opened 2026-03-22 17:18:28 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @Besi97 on GitHub (Aug 4, 2025).

I use the sync feature with the delete unmatched enabled, as I would like to ensure that Komodo has the same configuration that is committed to my repo. I would also like to be able to sync generic variables automatically from my repo, but I would not like to store secrets in the repo. So if I enable "Sync Variables", it wants to delete my secrets.

I would be fine with creating secrets manually, but I would like to leverage the sync feature for other variables that need to be shared between my actions. It would be great to be able to sync variables, but exclude secrets somehow. The "Match Tags" config on the sync could be a workaround if we could add tags to variables.

Thanks for considering and a huge thank you for this amazing tool!

Originally created by @Besi97 on GitHub (Aug 4, 2025). I use the sync feature with the delete unmatched enabled, as I would like to ensure that Komodo has the same configuration that is committed to my repo. I would also like to be able to sync generic variables automatically from my repo, but I would not like to store secrets in the repo. So if I enable "Sync Variables", it wants to delete my secrets. I would be fine with creating secrets manually, but I would like to leverage the sync feature for other variables that need to be shared between my actions. It would be great to be able to sync variables, but exclude secrets somehow. The "Match Tags" config on the sync could be a workaround if we could add tags to variables. Thanks for considering and a huge thank you for this amazing tool!
GiteaMirror added the enhancement label 2026-03-22 17:18:28 -05:00
Author
Owner

@rsocko commented on GitHub (Oct 17, 2025):

This would be very useful. I just had to recreate my Komodo server setup entirely and had all of my configuration saved to GitHub with the exception of the many variables & secrets. MVP for me would be to simply avoid synching the secrets. An enhanced version could sync the variable name and marked as a secret, but not store the actual value in GitHub (so that I would have an accurate set of variable names whether secrets or standard variables).

@rsocko commented on GitHub (Oct 17, 2025): This would be very useful. I just had to recreate my Komodo server setup entirely and had all of my configuration saved to GitHub with the exception of the many variables & secrets. MVP for me would be to simply avoid synching the secrets. An enhanced version could sync the variable name and marked as a secret, but not store the actual value in GitHub (so that I would have an accurate set of variable names whether secrets or standard variables).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#1315