Remote Taskfiles experiment

[pd93]

Warning

All experimental features are subject to breaking changes and/or removal at any time. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.

Note

You can view the Remote Taskfiles experiment documentation on our website, including instructions on how to enable/disable it.

Context

This experiment attempts to solve the problems originally described by #770.

Currently, Task only supports running Taskfiles located on the local filesystem. This makes it difficult to reuse Taskfiles across various repositories and systems without making copies of a file. It would be useful to have a way to run a Taskfile located on a remote system or run a local Taskfile that includes one on a remote system.

Proposal

This experiment would allow users to run a Taskfiles located elsewhere, such as via HTTP or in a remote Git repository. These remote Taskfiles can either be run directly from the CLI or included by another Taskfile.

We're looking to gather feedback on the current draft, so please feel free to leave your thoughts/comments here.

Decision log / TODOs:

• Refactor nodes as an interface feat: node refactor #1316
• HTTP nodes feat: remote taskfiles (HTTP) #1152
• Decide between go-getter or a native implementation
  • No go-getter for now. We can re-evaluate later
• How to handle security (remote files that change etc)
  • See https://taskfile.dev/experiments/remote-taskfiles/#security
• Caching (--download/--offline flags or similar)
  • See https://taskfile.dev/experiments/remote-taskfiles/#caching--running-offline
• Implement --yes flag on prompts feat: unify prompts #1344
• Decide if we should use remote/local files first if both are available feat: prefer remote taskfiles over cached ones #1345
• Consider storing checksums/cached files with a more user-friendly filename feat(remote): prefix checksums/cached files with the filename #1636
• Command to clear the remote cache feat(remote): add a command to clear the cache #1639
• Check that local -> remote -> remote:local includes work correctly feat: enable root remote taskfiles #1347
• Auto update TTL for cached files Feature Request: Have an auto update ttl for downloaded taskfiles #1402
• Add remote flags as config in Taskfile Feature request: Allow taskfile schema to use options related to remote taskfiles #1403
• Decide how special variables should look for remote files
• Running root remote Taskfiles feat: enable root remote taskfiles #1347
  • e.g. task test --taskfile https://raw.githubusercontent.com/go-task/task/main/Taskfile.yml
• Git Nodes
  • e.g. [email protected]/foo/bar?ref=main//Taskfile.yml feat(remote): support include git remote #1652

[task-bot]

This issue has been marked as an experiment proposal! 🧪 It will now enter a period of consultation during which we encourage the community to provide feedback on the proposed design. Please see the experiment workflow documentation for more information on how we release experiments.

[task-bot]

This experiment has been marked as a draft! ✨ This means that an initial implementation has been added to the latest release of Task! You can find information about this experiment and how to enable it in our experiments documentation. Please see the experiment workflow documentation for more information on how we release experiments.

[wburningham]

If one wants to use remote tasks in CI how does one bypass the prompt when running a task for the first time. Is there a flag or environment variable that can be set to “force yes” to the prompt on whether or not to include the remote task file?

BTW thanks for a great experiment!

[wburningham]

The documentation mentions the -y flag for tasks that require prompts, but the experimental documentation doesn't mention if that also applies to remote taskfile includes.

[pd93]

@wburningham Thanks for pointing this out. The --yes flag has not currently been set up to automatically accept the remote task prompts. This is definitely something we can consider in the next iteration. I think this is an acceptable change, but if anyone has any security concerns about being able to skip the remote taskfile warning prompts, please add a comment.

[oliver-helix]

For Running root remote Taskfiles, consider specifying the remote taskfile via the --taskfile arg?
task hello --taskfile https://raw.githubusercontent.com/go-task/task/main/Taskfile.yml

[oliver-helix]

Any idea why the following doesn't work?

# taskfile.yml
version: '3'

include:
  my-remote-namespace: https://raw.githubusercontent.com/go-task/task/main/Taskfile.yml

tasks:
  test:
    cmds:
      - echo test succesful

$ task --version
Task version: 3.30.1
$ task test
task: [test] echo test succesful
test succesful
$ export TASK_X_REMOTE_TASKFILES=1
$ task my-remote-namespace:packages
task: No tasks with description available. Try --list-all to list all tasks
task: Task "my-remote-namespace:packages" does not exist

[pd93]

@oliver-helix Good idea about the root remote taskfiles. As for why your example doesn't work. I think its just a simple typo:

  # taskfile.yml
  version: '3'

- include:
+ includes:
    my-remote-namespace: https://raw.githubusercontent.com/go-task/task/main/Taskfile.yml

  tasks:
    test:
      cmds:
        - echo test succesful

Edit: We should probably give a better error message for this...

[oliver-helix]

Doh! My bad. Thanks for the help! Consider updating the experiment docs to fix this typo.

[pd93]

Ah whoops. Well spotted. I've updated the docs 👍

[plcarman]

Hi, just wanted to say this experiment is exciting!

Do you have any plans to add support for remote endpoints that require authentication? My use case is that I have a remote Taskfile stored in GitLab. I would think an easy-ish way would be to honor my .netrc file like git and other tools do.

edit: I caught up on #1152 and I see there has already been talk about authentication. looking forward to whatever comes! Thanks.

[wburningham]

The --yes flag has not currently been set up to automatically accept the remote task prompts. This is definitely something we can consider in the next iteration. I think this is an acceptable change, but if anyone has any security concerns about being able to skip the remote taskfile warning prompts, please add a comment.

@pd93 my company is ready to try out taskfiles because the remote taskfile experiment moved to draft. Being able to run on CI with a --yes flag is our next implementation step.

When you say "the next iteration" are you wanting (or willing to accept) a PR?

The Experiments Documentation didn't specify any general timelines for accepting feedback/comments. Are you planning on waiting a minimum amount of time before releasing changes to this experiment?

[pd93]

@wburningham really nice to hear that this feature is making the difference for you. Are there any other blockers or features you'd need before being able to use this fully? (besides the obvious Git/SSH integration).

When you say "the next iteration" are you wanting (or willing to accept) a PR?

Absolutely! Contributions are always welcome, though we encourage people to discuss them first to make sure multiple people aren't doing the same thing and/or wasting their time. In this particular case, I actually already have a branch which will add this functionality and I intend to post a PR soon. As a potential future user of that functionality, your feedback on this would be very welcome.

If there are other extensions/improvements you'd like to help contribute to, I'm always happy to have some help.

The Experiments Documentation didn't specify any general timelines for accepting feedback/comments. Are you planning on waiting a minimum amount of time before releasing changes to this experiment?

There is no minimum/fixed time period for changes. @andreynering and I both work on this in our spare time, so planning is hard and changes tend to happen in chunks when we find some bandwidth. A new draft of the experiment will be released alongside the next version of Task which tends to happen around once a month, but this is also subject to our availability and having a set of meaningful changes to release.

I'm hoping to address the remaining TODOs in this issue (not the future extensions) in the next week or so and hopefully we'll get some good feedback from that which will allow us to move forward.

---

Edit - See PR:

• feat: unify prompts #1344

[pd93]

I've also just created #1345 which changes the default behaviour of Remote Taskfiles to prefer remote files over cached ones as discussed in previous PRs.

I've added a couple of thoughts to the end of the PR description. I would really appreciate feedback on this from @andreynering @ryancurrah @caphrim007 and anyone else with an opinion on the matter 🙏

[oliver-helix]

Any roadmap (ETA) for when remote taskfiles with Git ssh for private repository acecss will be added? Thanks so much for your hard work on this awesome project!

[ThomasSanson]

Greetings,

First and foremost, I would like to extend my heartfelt congratulations and gratitude for the exemplary work you have undertaken.

I am curious to know whether you have plans to support 'remote' Taskfiles that incorporate other Taskfiles. For instance, in this link: GitLab - Devcontainer Taskfiles, if a directory is segmented into multiple Taskfiles, will remotely including the principal Taskfile also entail the inclusion of the associated Taskfiles?

I look forward to your insightful response and thank you in advance for your consideration.

[lorenzofaresin]

Is it possible to add completion capabilities on remote tasks?

[vmaerten]

Hi!
Thanks for your work, it's a really really appreciated feature!
We plan to use it, to mutualize all our project's Takefile
Amazing work 🔥

[yordis]

I wonder if adding something like a shasum check would be a good idea here

[titpetric]

+1 for https://github.com/hashicorp/go-getter as the integration, seems like a good package, given a cursory review

…

On Wed, Mar 20, 2024, 05:29 Alex Ball ***@***.***> wrote: go-getter integration would be make go-task so much more useful for sharing tooling across our org. I think following the terraform cli's support for module sources <https://developer.hashicorp.com/terraform/language/modules/sources#generic-git-repository> would provide a validated approach to caching, auth, and featureset. go-getter supports a double slash syntax to specify a subpath of folders/archives/repos. Supporting this would be amazing to give scripts access to supporting files. Developers just need to set up native credentials for the source, and then could pull in all the team's tooling using a remote include and vars. And any repo-specific tooling would remain in there For caching, terraform always uses the local module path and exits with an error if it's missing. You run terraform init to download remote sources once, and whenever versions change. These sources are stored under the ignored tool folder, .task in this case. This makes it straightforward to debug since you can view the code locally. To match the current behavior, go-task would download source by default, unless you used --download and --offline to try only the local version. — Reply to this email directly, view it on GitHub <#1317 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABY7EHWLPLEP5YZ7ARGQZ3YZEGD7AVCNFSM6AAAAAA4CZOYE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBYGY2DKMJUGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[vmaerten]

I've started working on adding support of Git in remote taskfile.

If you want to try it out, you need to clone my repo https://github.com/vmaerten/task, switch to remote-git branch, and run go run ./cmd/task -d <your_dir>

We will support SSH url, SCP url and HTTPS url.
You can find the docs here : https://github.com/vmaerten/task/blob/4f85e85167b375100e3da3803973ff203045935e/website/docs/experiments/remote_taskfiles.mdx?plain=1#L65

I'll add more examples in the next couple of days.

[blackjid]

That is awesome @vmaerten thank for the work...

Why did you choose to set the filename and the git reference in the same querystring in the url? Why not just having a different querystring for the filename? https://github.com/foo/bar.git?ref=main&filename=directory/Taskfile.yml

Or if you don't want the extra query string, a more readable form I think could be to add the path to the file just after the .git https://github.com/foo/bar.git/directory/Taskfile.yml?ref=main maybe with a double slash // like terraform and others does.. https://github.com/foo/bar.git//directory/Taskfile.yml?ref=main

Sorry if this is not the place or time to give feedback. Maybe discord?

[vmaerten]

Hello @blackjid
Thanks a lot for your feedback. I've forgot to put the PR's URL here. I'll copy / past your comment there and we can discuss on it the PR

[d3nnxs]

Hi,
First of all thanks for this project and work. I really appreciate this project. After replacing most of my make files I also plan to move CI/CD to Taskfile. In my case it is GitLab CI.

I wonder if it is possible to have something like a provider pattern for including remote files? With knowing the provider it would be possible to parse required credentials from CI environment variables during the include. This would make it easier for the user to handle the secrets.

Example:

includes:
  example: 
    provider: gitlab
    url: gitlab.my-org.com # for self-hosted variants, should default to SaaS
    project: my-group/project
    file: Taskfile.yaml
    ref: main

It's just an idea from the user's perspective. I have not yet been able to take a look at the code to say how well this can be implemented.

[jlucktay]

I've just taken my PR for cache TTL implementation out of draft, and it's ready for review now.

[sebastianbuechler]

This looks indeed promising. Since we have most of our tasks quite generic (not coupled to one repo) it would be interesting to define a remote namespace as default so that task remote-namespace:my-task would convert to task my-task directly.

[vmaerten]

A PR is in progess to add a Flatten include (#1704) It'll be possible to combine remote with flatten.

[Kieranties]

Hi all - firstly thanks for the significant progress here, I'm eager to make use of this feature when it reaches maturity!

I've been building a few task utilities across multiple projects and am now beginning the work in normalizing usage now that some consistent patterns have emerged. The remote taskfile feature is exactly what I need to get this done.

I can be certain that a developer will have the github cli installed and intend to use that to source the users authentication token, the intent being it can then be used in the url of the remote file. However, it would seem that the environment parameters configured in the task file are not resolved before the remote includes.

For example, the following works:

# yaml-language-server: $schema=https://taskfile.dev/schema.json
version: '3'
output: prefixed

env:
  GH_TOKEN:
    sh: gh auth token

tasks:
  init-deps:
    desc: Initialize and update the project dependencies
    cmds:
      - echo {{.GH_TOKEN}}

The console displays the token returned from the github cli.

However the following does not work:

# yaml-language-server: $schema=https://taskfile.dev/schema.json
version: '3'
output: prefixed

env:
  GH_TOKEN:
    sh: |
      gh auth token

includes:
   remote-source: https://{{.GH_TOKEN}}@raw.githubusercontent.com/ORG/REPO/BRANCH/taskfile.yml

tasks:
  init-deps:
    desc: Initialize and update the project dependencies
    cmds:
      - task: remote-source:init-deps

The output of which is task: No Taskfile found at "https://@raw.githubusercontent.com/ORG/REPO/BRANCH/taskfile.yml"

I can see that the work from @vmaerten may well render this path obsolete (and I would be happy not to follow it) but I'm unsure if this is an issue in task itself, or the implementation of remote includes

[Kieranties]

Additionally, a note on this warning message

The task you are attempting to run depends on the remote Taskfile at "https://[email protected]/stadionHQ/tasks/main/terraform.taskfile.yml".
--- Make sure you trust the source of this Taskfile before continuing ---
Continue? [y/N]

The REDACTED string is not actually redacted in the console output. It would be good if any urls that may be presented in the outputs could be checked for authentication details prior to the domain and strip them out.

[pbitty]

Hello, we have been experimenting with go-task at my workplace (Wattpad) and are looking into incorporating it into our CI/CD workflows. Thanks for creating such a useful tool! The features are really well thought out. I have a proposal:

We are looking for the ability to pull supporting files along with our remote Taskfile. We could build a separate tool for this, but it seems so close to what “remote taskfiles” provides that it could be a part of the same feature. In essence, we treat the remote Taskfile as a “remote bundle” that includes the whole directory along with the Taskfile. This allows us to include shared scripts and configuration files, alongside the Taskfile that exposes them.

I did a prototype where I reference a folder on github, and Task will:

• Download the whole folder into .task/cache/...
• Look for a default Taskfile name following the same rules as the root file (eg. Taskfile.yaml, Taskfile.dist.yaml, etc)
• Parse this file as the included file
• Resolve the taskfile path variables in the same way as local includes, such that one can reference the root taskfile path or the included taskfile path easily (ie: using .ROOT_TASKFILE, .ROOT_DIR, .TASKFILE, .TASKFILE_DIR)

This gives us the ability in the included file to reference other bundled files using paths based on .TASKFILE_DIR. In a way, this makes remote taskfile includes behave like local includes when it comes to the .TASKFILE_DIR variable.

The feature can remain optional and compatible with the single-remote-taskfile case by supporting both “folder” and “file” references. For example (using pseudo-URLs, not an actual format):

• when we reference github.com/org/repo/some/path/Taskfile.yaml, it will download only the single file (what we have today)
• when we reference github.com/org/repo/some/path, it will download the whole folder and look for a “standard” Taskfile name in there. (If we wanted a non-standard Taskfile name, that could be an optional parameter.)

How do you feel about incorporating this feature?

My proposal is that I put in the time to help design it, implement it, and submit necessary PRs (with others’ input of course).

Related to this, the go-getter library (mentioned above) would lend to this very well, as it is designed to download files and directories (or archives), and it handles other requests from this thread (authentication, other providers beyond HTTP). I would explore this option and satisfy both goals at the same time. If you would like to see any prototype PRs first to get a sense for how it would look and feel, I could do this as well.

Would you be open to this?

/cc @vmaerten - this would supersede #1652, but doesn't have to block it being merged if the syntax is compatible. Thanks for doing this work!

[pbitty]

I've started a draft implementation of the above in #1774. I would love to discuss the design with someone, and if we get some consensus I can continue implementing.

[mgbowman]

@vmaerten I've been testing your work from #1652 for remote git support and want to surface two minor issues and get some feedback.

Cannot use commit hash for ref

As of today, you cannot use a commit hash in ref (at least I couldn't get it to work)

includes:
  task: https://gitlab.com/group/project.git//Taskfile.task.yml?ref=987bc7ff4184c9f2a17242255fe048fc1ab93089

gives the error

couldn't find remote ref "refs/heads/987bc7ff4184c9f2a17242255fe048fc1ab93089"

I believe the source of this comes from go-git clone which calls cloneRefSpec and IIUC that switch, a hash cannot be used as the cases will evaluate to...

Case	Refspec
o.Mirror	+refs/*:refs/*
o.SingleBranch && o.ReferenceName == plumbing.HEAD	+HEAD:refs/remotes/{remote}/HEAD
o.SingleBranch	+refs/heads/{ref}:refs/remotes/{remote}/{ref}
default	+refs/heads/*:refs/remote/{remote}/*

The 3rd case o.SingleBranch is where we land today.

I am stuck here.

Password is logged in clear text when prompting to trust the remote source

This also happens when using --verbose

When using basic auth with https, the {user}:{password} is logged to the terminal in clear-text ...

includes:
  task: https://git:{{.TOKEN}}@gitlab.com/group/project.git//Taskfile.task.yml

outputs

The task you are attempting to run depends on the remote Taskfile at "https://git:[email protected]/group/project.git//Taskfile.task.yml".

I've tracked this to GitNode.Location() returning rawUrl

Two possible alternatives (not sure of the implications)

1. Use URL.Redacted() but you lose the path and/or ref

func (node *GitNode) Location() string {
	return node.URL.Redacted()
}

will output

The task you are attempting to run depends on the remote Taskfile at "https://git:[email protected]/group/project.git".

2. Construct the URL from its parts

func (node *GitNode) Location() string {
	l := fmt.Sprintf("%s://%s/%s//%s", node.URL.Scheme, node.URL.Host, node.URL.Path, node.path)
	if node.ref != "" {
		l += fmt.Sprintf("?ref=%s", node.ref)
	}
	return l
}

will output

The task you are attempting to run depends on the remote Taskfile at "https://gitlab.com/group/project.git//Taskfile.task.yml".

---

Task version: v3.39.3-0.20240924174559-e619bad4a9fb (h1:iJZzplUCicBgTdzcfKEIc4KrF/cp/XLquiJX/IoeNDA=)
Operating system: Linux 6f588dd-lcelt 6.8.0-45-generic #45~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Sep 11 15:25:05 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Experiments enabled: ENV_PRECEDENCE GENTLE_FORCE REMOTE_TASKFILES

[pbitty]

1. Use URL.Redacted() but you lose the path and/or ref

@mgbowman , when I try URL.Redacted() I still get the path and ref. Here's an example: https://play.golang.com/p/kc_Qo9RFo8K

I wonder why in your case it didn't come out.

[pbitty]

I have two separate suggestions for this feature. I would love to hear people's thoughts on them.

1. Enable downloading directories from git.

This would allow remote Taskfiles to include supporting files (scripts, configs, etc.)

2. Only download files if not in cache, or if requested via --download.

I believe this behaviour is less surprising and more similar to other tools (the best example I can think of is Docker) and it really speeds things up. I believe it also makes for a smoother UX because once it's cached it just works and you don't get interrupted by a prompt if the upstream changes.

(I prototyped number 1 above but the proposal it was quite wordy. I am boiling this message down to the essentials.)

[c-ameron]

I'm a big fan of number 2!

[mgbowman]

Number 2 will be trivial with the next release as there's a TASK_OFFLINE=1 var you can set.

You'll have to run task --offline=false --download --yes but I think that's acceptable.

[pbitty]

You'll have to run task --offline=false --download --yes but I think that's acceptable.

Is this what you have to run to force it to download the first time?

[vmaerten]

@mgbowman Thanks for your feedback! I'll take a look at it :)

@pbitty Yes, @mgbowman is right. In the next version, you will always be able to use the cached taskfile instead of the remote one by setting TASK_OFFLINE=1.

If you want to force a fresh copy, you can either run TASK_OFFLINE=0 task ... or task --offline=false ...

Note: --download will download a fresh copy but won't execute any task. --download is mutually exclusive with --offline.

[pbitty]

Regarding my suggestion above:

1. Enable downloading directories from git.
   This would allow remote Taskfiles to include supporting files (scripts, configs, etc.)

@andreynering @pd93 @vmaerten, are you open to the idea? If so, I propose the following:

• I would create a PR extending the current git functionality (and not do anything bigger using go-getter)

• The scheme would remain the same and use the path after //

• If the path is a directory, eg:

  https://github.com/org/repo.git//some/directory?ref=main
  

  Then the whole directory gets downloaded and we look for a "default" Taskfile in the directory (from the list of defaults).

• If the path refers directly to a file, eg:

  https://github.com/org/repo.git//some/directory/Taskfile.yml?ref=main
  

  Then only the file will be downloaded. This allows the existing single-file usage to continue to work the same way.

What do you think?

(There are details to iron out, like how files are stored and checksummed, but I think that can be better addressed in a draft PR.)

[nikaro]

edit(duplicate): my bad i just saw #1317 (comment) that already report this issue.

---

Hello,

The git remote include does not seem to work with tags and commits (at least GitHub HTTPS scheme).

This works:

includes:
  lint:
    taskfile: https://github.com/nikaro/meta.git//taskfiles/lint.yml?ref=main
    internal: true

This (using a tag) does not work:

includes:
  lint:
    taskfile: https://github.com/nikaro/meta.git//taskfiles/lint.yml?ref=tasks-v1
    internal: true

This (using a commit hash) does not work:

includes:
  lint:
    taskfile: https://github.com/nikaro/meta.git//taskfiles/lint.yml?ref=6383d5ce51cf21dea72aab6190e6e112e7249940
    internal: true

Is this intended or am i doing something wrong?

[mikarl]

@nikaro I got it working with tags, not sure if it is possible with a commit hash.

Internally the implementation is using go-git, see https://pkg.go.dev/github.com/go-git/go-git/v5/plumbing#ReferenceName

Meaning you can do branches like

includes:
  lint:
    taskfile: https://github.com/nikaro/meta.git//taskfiles/lint.yml?ref=refs/heads/main
    internal: true

And tags like

includes:
  lint:
    taskfile: https://github.com/nikaro/meta.git//taskfiles/lint.yml?ref=refs/tags/task-v1
    internal: true