-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Require local provider in tests #2953
Conversation
Does the PR have any schema changes?Does the PR have any schema changes?Looking good! No breaking changes found. Maintainer note: consult the runbook for dealing with any breaking changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, nice this is a good stop-gap while we still use the $PATH.
The long term aim here is to ditch ever relying on the $PATH and rather use either:
- Starting the provider first then connecting the test to the running provider via
PULUMI_DEBUG_PROVIDERS
. - Using the plugin configuration section of the
Pulumi.yaml
to specify where to run the provider from.
Either of these approaches is preferred in the long term as their failure mode is more predictable - if the explicitly specified provider is not found, then the whole run immediately fails as we can also disable using ambient providers.
This PR adds a new make target for providers `provider_no_deps` - this one will just run the go build command without `tfgen` and `install_plugins`. This is needed since `tfgen` and `install_plugins` have no caching, so will rerun each time and I'd like to use the `go build` in pulumi/pulumi-aws#2953
This PR adds a test main for the aws provider which checks that the aws provider used in the tests is a local one.
The default behaviour is for the pulumi binary to download a provider which leads to some quite confusing behaviour.