[Feature] Support Resolving Extension Repo References

[iamnande]

Howdy 👋🏻,

When referencing an v1alpha1.extension, using load(), that comes from an v1alpha1.extension_repo I am receiving:

loading extension env_args: no extension tiltfile found at /Users/iamnande/Library/Application Support/tilt-dev/tilt_modules/github.com/tilt-dev/tilt-extensions/env_args/Tiltfile

Example block that can produce the error:

## Extensions
v1alpha1.extension_repo('foo', url='https://github.com/iamnande/foo/tilt-extensions')
v1alpha1.extension(name='bar', repo_name='foo', repo_path='bar')
load('ext://bar', 'do_cool_thing')

It would be neat if it either didn't yell at me or if it resolved the extension.

Running tilt up in any form handles all the custom references just fine so no actual workflow is being impeded.

[nicksieger]

I can think of a couple questions/issues here.

1. For this to work reliably, I think we'd have to assume that you have Tilt already running with this Tiltfile. Then we can query Tilt's API for all registered extension_repos and extensions in order to resolve the file paths. Would that be ok?
2. If Tilt isn't available, should the diagnostic be a warning instead of an error? Should we have a config setting to turn off errors or warnings about unknown or missing extensions?

[iamnande]

I can think of a couple questions/issues here.

1. For this to work reliably, I think we'd have to assume that you have Tilt already running with this Tiltfile. Then we can query Tilt's API for all registered extension_repos and extensions in order to resolve the file paths. Would that be ok?

I think this would definitely be reasonable. There's likely a few integrations required, not available in vsc, in order to effectively resolve the extensions.

2. If Tilt isn't available, should the diagnostic be a warning instead of an error? Should we have a config setting to turn off errors or warnings about unknown or missing extensions?

A configuration to ignore these would be helpful or maybe extension_repos and extensions can be warnings by default?

[flamein]

As a dirty workaround, you can symlink your extension in the tilt-dev repo /Users/$USER/Library/Application Support/tilt-dev/tilt_modules/github.com/tilt-dev/tilt-extensions

cd /Users/$USER/Library/Application Support/tilt-dev/tilt_modules/github.com/tilt-dev/tilt-extensions
ln -s ../../user/tilt-extensions/<extension>

Don't tell people I told you to do this

[gayanper]

I would recommend we don't show errors for custom repos until a Tilt is running for this file. I assume the LS is parsing the file which might be able to figure out which entries are part of custom repositories by their names. That would work really neatly.