@denbeigh2000 could you create a Terraform module to accomplish this instead?

that'd work if i were willing to split the module out into another repository and import it, but it leaves a few shortcomings:

• i can't include a terraform module from ../ between these templates
• i can't make use of common files (e.g., scripts, configuration files, etc) that may be used elsewhere in a shared monorepo

Ahh, I see. I wonder if it'd be best to upload the entire directory as a template, and be able to specify a subdirectory to execute out of?

that's totally reasonable for the linked case, but there are some valid use cases where this doesn't make sense

e.g., $WORK uses a large, shared monorepo, and there are often resources in far-flung relative directories (e.g., ../../../../resources/some-other-team/some-other-product/resource.yml) that we want to include - an approach like this would require committing nearly the entire repository as a template.

would it be possible to resolve file() resources and include them in the uploaded tarball, so that they can be used in the template?

What if the tarring process traversed symlinks?

I'd have no issue with making a few relative symlinks to address this 👍

After #5720 is in you'll be able to do:

tar -cvh . | coder templates <push|create> -d - <name>

Thank you very, very much 🙏

I like this feature, thanks @denbeigh2000

What if the tarring process traversed symlinks?

As per my understanding, doing a tar of directory to push template is the only option to follow symlinks as coder templates push does not follow symlinks, correct?

What if the tarring process traversed symlinks?

As per my understanding, doing a tar of directory to push template is the only option to follow symlinks as coder templates push does not follow symlinks, correct?

That's correct. In general we don't want to go feature-to-feature with tar, so we promote using that for all advanced directory serialization.

Good, it does work with this way:

tar -cvh . | coder templates push ..

Thanks!