-
Notifications
You must be signed in to change notification settings - Fork 155
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
Panic provisioning aws:ec2:VpcEndpoint on AWS V6.0 #2658
Comments
That stacktrace looks like a pulumi-aws issue rather than the CLI? |
@Frassle customer responded with |
Yeah. This looks like a provider panic, I'll transfer it to pulumi-aws. It's interesting that it's using java. |
Unfortunately, Java has a limitation that it automatically upgrades to -alpha releases. The workaround is to pin a latest production release of pulumi-aws, v5.42.0 |
I took at stab in reproducing this but I'm having trouble reproducing. The program I came up with is package myproject;
import java.util.Map;
import com.pulumi.Pulumi;
import com.pulumi.resources.CustomResourceOptions;
import com.pulumi.core.Output;
import com.pulumi.aws.s3.Bucket;
import com.pulumi.aws.ec2.Vpc;
import com.pulumi.aws.ec2.VpcArgs;
import com.pulumi.aws.ec2.VpcEndpoint;
import com.pulumi.aws.ec2.VpcEndpointArgs;
import com.pulumi.aws.ec2.inputs.VpcEndpointDnsOptionsArgs;
public class App {
public static void main(String[] args) {
Pulumi.run(ctx -> {
var defaultVpc = new Vpc("mainvpc", VpcArgs.builder()
.cidrBlock("10.0.0.0/16")
.enableDnsHostnames(true)
.enableDnsSupport(true)
.build());
var defaultVpcId = defaultVpc.getId();
var vpce = new VpcEndpoint("secretsManagerVPCEdpoint", VpcEndpointArgs.builder()
.dnsOptions(VpcEndpointDnsOptionsArgs.builder()
.dnsRecordIpType("ipv4")
.build())
.ipAddressType("ipv4")
// .policy("{}")
.privateDnsEnabled(true)
// .securityGroupIds(Output.all(asmVpcEndpointSecurityGroup.id()))
.serviceName("com.amazonaws.us-east-1.secretsmanager")
// .subnetIds(getPrivateSubnetIds(defaultVpc))
.tags(Map.of("Name", "secrets manager endpoint"))
.vpcEndpointType("Interface")
.vpcId(defaultVpcId)
.build(), CustomResourceOptions.builder()
// .protect(true)
.build());
});
}
} I tried it under both the last released version and the cited version:
I tried adding/removing tags. In all the combinations I'm not able to hit the panic. It seems from the stack trace that this is executing Update part of the plan, so I tried updates, but no luck so far. I tried an Upgrade test from 5.* to 6.* on a provisioned program, also no luck. |
One set of possibilities I did not test is perhaps default (provider-level) tags are in play somehow. Currently unable to set them to test out due to |
Looks like #2663 was invalid, it's still possible to try defaultTags here. Unfortunately I need to pivot for the rest of the week, back to this on Monday. |
Deeper investigation reveals this is a duplicate of pulumi/pulumi-terraform-bridge#1033 that was fixed after the issue was discovered. Where the panic originates:
Recent fix to not panic on GetRawPlan: Merged to AWS in: Affected commit is on v3.54.1: Line 11 in 8163083
|
What happened?
Customer experienced a panic after upgrading to Pulumi CLI v3.76.1:
Expected Behavior
No panic.
Steps to reproduce
Code snippet:
Output of
pulumi about
Additional 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: