← Back to all posts

Support dynamic VCS repository input in Templates

Templates currently resolve the VCS repository field at publish time, meaning the repository is baked into the template version and can't be provided as a dynamic input. This prevents using Templates for use cases where the same stack configuration needs to be deployed across multiple repositories - e.g. a "Stack Vendor" template that engineers deploy from to onboard their repo.

Workaround
We manage stack vendor stacks centrally in a Terraform config with for_each, and engineers open PRs to add their repo. This works but removes the self-service aspect that Templates are designed for.
Problem
We want to enable self-service stack creation where engineers deploy a standardized stack vendor template into their own repo's space. The stack configuration is identical across repos (OpenTofu, autodeploy, worker pool, role attachments, etc.) - the only difference is the target repository. Since the repository can't be a template input, we can't use Templates for this and have to manage stack vendors centrally via Terraform instead.

Please authenticate to join the conversation.

Upvoters
Status

🔭 Discovery

Board

💡 Feature Requests

Tags

Stacks

Date

3 days ago

Subscribe to post

Get notified by email when there are changes.