Add capability to configure/run an initial resource sync on startup. #552

New Issue

GiteaMirror · 2025-10-31T15:15:09-05:00

GiteaMirror commented

2025-10-31 15:15:09 -05:00

Originally created by @leefr on GitHub (Sep 2, 2025).

In order to bootstrap a pre-configured system with many resources, it is currently necessary to either use the UI or script something via the API in order to configure/trigger the initial resource sync. By including a mechanism to configure an initial sync of pre-defined resources in the core configuration or via environment variables, it would become much simpler/easier to create turnkey configurations that don't require end-user knowledge nor create possible timing issues for the API script writer.

Originally created by @leefr on GitHub (Sep 2, 2025). In order to bootstrap a pre-configured system with many resources, it is currently necessary to either use the UI or script something via the API in order to configure/trigger the initial resource sync. By including a mechanism to configure an initial sync of pre-defined resources in the core configuration or via environment variables, it would become much simpler/easier to create turnkey configurations that don't require end-user knowledge nor create possible timing issues for the API script writer.

GiteaMirror added the enhancement label 2025-10-31 15:15:09 -05:00

GiteaMirror commented

2025-10-31 15:15:10 -05:00

@iustin05 commented on GitHub (Sep 13, 2025):

I've been trying to migrate to Komodo exactly because of the 'fully-as-code' infrastructure approach. The only thing I'm missing is exactly this, being able to pass a resource_sync inside of the core.config.toml.

Another thing I would consider is having the option to opt for a single config file for all the Komodo 'swarm' (without going through all of the syncs config)... Imagine that, one TOML file (with the peripheries filled in), internal-only subnet for predictive networking and you get all your stacks/deployments ready with one terraform command 💯

@iustin05 commented on GitHub (Sep 13, 2025): I've been trying to migrate to Komodo exactly because of the 'fully-as-code' infrastructure approach. The only thing I'm missing is exactly this, being able to pass a [[resource_sync]] inside of the core.config.toml. Another thing I would consider is having the option to opt for a single config file for all the Komodo 'swarm' (without going through all of the syncs config)... Imagine that, one TOML file (with the peripheries filled in), internal-only subnet for predictive networking and you get all your stacks/deployments ready with one terraform command 💯

GiteaMirror referenced this issue

2025-10-31 15:20:43 -05:00

[PR #552] [CLOSED] feat: add musl support for periphery builds #747

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#552