A proposition to enable this feature by specifying a custom file path for the task configuration.

[btpemercier]

A proposition to enable this feature by specifying a custom file path for the task configuration.

Example 1: Local Path

[build]
alias = "b"
file = "./path/to/build"

The task configuration is located in a relative path (./path/to/build) or an absolute path (/path/to/build).

Example 2: Remote HTTP/HTTPS URL

[deploy]
alias = "d"
file = "https://example.com/modules/deploy"

This example fetches the task configuration from a remote HTTP/HTTPS location.

Example 3: Git Repository (HTTPS)

[analyze]
alias = "a"
file = "git::https://github.com/user/repo.git//path/to/task?ref=main"

This pattern uses the git:: prefix to fetch the configuration from a Git repository. The // indicates the path within the repository, and the optional ?ref=main specifies the branch or tag to use.

Example 4: Git Repository (SSH)

[package]
alias = "p"
file = "git::ssh://git@github.com:user/repo.git//path/to/task?ref=develop"

For private repositories, the git::ssh:// prefix enables access using SSH. The ref=develop can point to a specific branch, tag, or commit.

Example 5: S3 Bucket

[cleanup]
alias = "c"
file = "s3::https://s3.amazonaws.com/my-bucket/modules/cleanup"

This format ensures consistency with Terraform's familiar URL patterns, making it intuitive for users already accustomed to those conventions.

Originally posted by @rodvieirasilva in #2488 (comment)

[jdx]

we already have the first 2, that's all I'm interested in building at the moment

[btpemercier]

I'm agree with you on the first point, but the answer let me disappointed, I know its your project and you spent a lot of time to maintain and improve it.

But do you consider this major feature in the future or not ?

Maybe we can contribute to the project by implementing part of the feature and exchange here about the need and what the community wants

[jdx]

I would certainly accept a pr for the others