Not possible to deny default providers in 1.0.0-beta11 #930
Comments
Oro
added
kind/bug
|
Hi @Oro - thank you for opening this issue. We'll look into it as soon as we can. |
|
I think this might be another instance of the issue where explicit providers are not inherited correct - in the component framework - pulumi/pulumi#10640 This will be able to be resolved once that issue is fixed and we can make a new release. |
danielrbradley
added
the
awaiting-upstream
11093: Improve the error for a denied component provider r=iwahbe a=iwahbe <!--- Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the [CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md) documentation. --> # Description <!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. --> This improves the error message for pulumi/pulumi-awsx#930. ## Checklist <!--- Please provide details if the checkbox below is to be left unchecked. --> - [ ] I have added tests that prove my fix is effective or that my feature works <!--- User-facing changes require a CHANGELOG entry. --> - [ ] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change <!-- If the change(s) in this PR is a modification of an existing call to the Pulumi Service, then the service should honor older versions of the CLI where this change would not exist. You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add it to the service. --> - [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version <!-- `@Pulumi` employees: If yes, you must submit corresponding changes in the service repo. --> Co-authored-by: Ian Wahbe <ian@wahbe.com>
|
Upstream issue seems resolved. Will this be in the next beta release? |
danielrbradley
removed
the
awaiting-upstream
|
Yes, this should be fixed in the next release once we're upgraded dependencies. This should be happening quite soon. |
|
After upgrading to |
|
Are you testing this on a new or existing stack? An existing stacks may contain references to the old version of the awsx plugin from existing resources and might required a re-deploy to pull in the new provider version. If this is still persisting, we can raise this again in https://github.com/pulumi/pulumi |
|
The dependency versions are: I have set Still results in |
|
Here's a quick status update and workaround: As of the 1.0.0 beta and later, AWSx is implemented as a component package so it can be used by all Pulumi languages, which means it has an associated awsx provider plugin. As such, when using the feature to disable all default providers, you'll get an error when not specifying an explicit awsx provider for any AWSx components created in a stack: To address this, you'd have to specify an explicit awsx provider for the AWSx component, as well as an explicit aws provider for the component's children, something like: import pulumi
import pulumi_aws as aws
import pulumi_awsx as awsx
awsxProvider = awsx.Provider("awsxProvider")
awsProvider = aws.Provider("awsProvider")
awsx.ec2.Vpc("vpc", opts=pulumi.ResourceOptions(provider=awsxProvider, providers=[awsProvider]))Unfortunately, this doesn't currently work due to a limitation that prevents specifying an explicit provider for packaged components: pulumi/pulumi#11520. WorkaroundIn the meantime, the best workaround when using config:
pulumi:disable-default-providers:
- aws
- kubernetesSince And then specify the explicit provider to use for the component's children: import pulumi
import pulumi_aws as aws
import pulumi_awsx as awsx
awsProvider = aws.Provider("awsProvider")
awsx.ec2.Vpc("vpc", opts=pulumi.ResourceOptions(provider=awsProvider)) # or: opts=pulumi.ResourceOptions(providers=[awsProvider]) |
thomas11
added
the
awaiting-upstream
|
Will this be solved with pulumi/pulumi#13282? |
What happened?
Denying all default providers via the following stack configuration does not allow me to instantiate e.g. a VPC (I also tried it with a cloudtrail, presumably others also don't work).
Steps to reproduce
{ "name": "awsx-default-provider", "main": "index.ts", "devDependencies": { "@types/node": "^14" }, "dependencies": { "@pulumi/pulumi": "^3.0.0", "@pulumi/aws": "^5.0.0", "@pulumi/awsx": "^1.0.0-beta" } }Expected Behavior
Pulumi should create the vpc with the supplied provider config.
NB: With awsx 0.40 using the aws provider with the following works:
{ "name": "awsx-default-provider", "main": "index.ts", "devDependencies": { "@types/node": "^14" }, "dependencies": { "@pulumi/pulumi": "^3.0.0", "@pulumi/aws": "^5.0.0", "@pulumi/awsx": "^0.40" } }Actual Behavior
Output of
pulumi aboutAdditional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: