rapid-raincoat-36492
01/14/2022, 9:17 PMhundreds-article-77945
01/15/2022, 12:59 AMmysterious-dawn-40701
01/16/2022, 9:24 AMtimeout removing Node Template: Bad response statusCode [405]. Status [405 Method Not Allowed]. Body: [baseType=error, code=MethodNotAllow, message=Template is in use by a node.]
Is there any way to influence what order destroy will usemysterious-dawn-40701
01/16/2022, 9:25 AMmost-lighter-95902
01/16/2022, 5:51 PMpulumi up
in multiple stacks in parallel?magnificent-lifeguard-15082
01/16/2022, 8:40 PMFileArchive
then pulumi will have a hard time on another machine and will fail to update 😬 Is this expected? If so might be worth adding a warning or explicit mention of relative path requirement on the docs. I do wonder how we should handle non-deterministic paths though between builds? I have a "file not found" error where a BucketObject
is referencing a .zip
with an absolute path which was created running up
on another machine.most-lighter-95902
01/17/2022, 12:06 AMquick-fall-21011
01/17/2022, 12:36 AMpulumi up
which then also triggers a kubernetes deployment. All highly inefficient. Here's how I build:
//context "../../../src/AppABC"
var imageName = Output.Format($"{_registryServer}/{imageBaseName}");
var image = new Image($"{appName}-image", new ImageArgs
{
Build = new DockerBuild { Context = context },
ImageName = imageName,
Registry = new ImageRegistry
{
Server = _registryServer,
Username = _registryUsername,
Password = _registryPassword
},
});
future-daybreak-16512
01/17/2022, 5:25 AMripe-park-70944
01/17/2022, 11:56 AMmagnificent-lifeguard-15082
01/17/2022, 12:14 PMcool-jewelry-33023
01/17/2022, 3:58 PMpulumi config set
in a CI/CD pipeline to update the tag of the Docker image.
The tag format is the build number we're using - YYYYMMDD.r
where r
is the build iteration in that day - for example - 20220117.1
The problem is that since a few days ago pulumi CLI started saving the value as 2.02201171e+07
Any idea what to do with this? 😄echoing-midnight-60897
01/17/2022, 4:07 PMError Invoke of 'aws:ssm/getParameter:getParameter' failed: rpc error: code = Unknown desc = invocation of aws:ssm/getParameter:getParameter returned an error: invoking aws:ssm/getParameter:getParameter: Error describing SSM parameter: ParameterNotFound:status code: 400
error: update failed
I’ve verified the parameters, IAM permissions and values of the parameters and everything seems to be fine. It doesn’t give any parameter to check in specific where the error log isn’t being helpful.
Any idea on how this can be resolved?breezy-appointment-80121
01/17/2022, 9:25 PMeager-gigabyte-20835
01/17/2022, 10:06 PMfast-pager-93865
01/18/2022, 7:03 AMprivateSubnet, err := ec2.NewSubnet(ctx, fmt.Sprintf("eks-subnet-private-%d", i), &ec2.SubnetArgs{
VpcId: vpc.ID(),
CidrBlock: pulumi.String(fmt.Sprintf("%s.1%d.0/24", netWork, i)),
AvailabilityZone: pulumi.String(zone),
MapPublicIpOnLaunch: pulumi.Bool(true),
Tags: GetTags(ctx, fmt.Sprintf("eks-%s-subnet-private-%d", environment, i)),
})
if err != nil {
return err
}
however i haven't quite mastered what should be passed into my EKS. I was assuming a list of private subnets retrieved by using the Apply, but I can't quite put together what that should look like.
for example
eksCluster, err := eks.NewCluster(ctx, "eks-cluster", &eks.ClusterArgs{
RoleArn: pulumi.StringInput(eksRole.Arn),
VpcConfig: &eks.ClusterVpcConfigArgs{
PublicAccessCidrs: pulumi.StringArray{
pulumi.String("0.0.0.0/0"),
},
SecurityGroupIds: pulumi.StringArray{
clusterSg.ID().ToStringOutput(),
},
SubnetIds: privateSubnets, << here is my issue
},
})
if err != nil {
return err
}
Any help most welcome!
Thank youmagnificent-lifeguard-15082
01/18/2022, 2:27 PMService(..., dependsOn: migrationLambdaRun)
Edit: Found the command package 🙂hundreds-rocket-82425
01/18/2022, 5:37 PMec:index:Deployment (x):
error: ec:index/deployment:Deployment resource 'x' has a problem: Value for unconfigurable attribute: Can't configure a value for "elasticsearch.0.topology.0.node_roles": its value will be decided automatically based on the result of applying this configuration.. Examine values at 'Deployment.Elasticsearch.Topology[0].NodeRoles'.
error: ec:index/deployment:Deployment resource 'x' has a problem: Value for unconfigurable attribute: Can't configure a value for "elasticsearch.0.topology.0.instance_configuration_id": its value will be decided automatically based on the result of applying this configuration.. Examine values at 'Deployment.Elasticsearch.Topology[0].Instanc
eConfigurationId'.
error: ec:index/deployment:Deployment resource 'x' has a problem: Value for unconfigurable attribute: Can't configure a value for "elasticsearch.0.topology.0.autoscaling.0.policy_override_json": its value will be decided automatically based on the result of applying this configuration.. Examine values at 'Deployment.Elasticsearch.Topology[0
].Autoscaling[0].MaxSize'.
error: ec:index/deployment:Deployment resource 'x' has a problem: Value for unconfigurable attribute: Can't configure a value for "elasticsearch.0.topology.0.config": its value will be decided automatically based on the result of applying this configuration.. Examine values at 'Deployment.Elasticsearch.Topology[0].Config'.
polite-napkin-90098
01/18/2022, 7:49 PMpulumi import aws:ec2/route:Route mon2bdefa rtb-0173c706be3_10.3.0.0/16
But it results in:
Previewing import (infra-top):
Type Name Plan Info
pulumi:pulumi:Stack infra-infra-top 1 error
= └─ aws:ec2:Route mon2bdefa import 11 errors
Diagnostics:
pulumi:pulumi:Stack (infra-infra-top):
error: preview failed
aws:ec2:Route (mon2bdefa):
error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "egress_only_gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.EgressOnlyGatewayId'.
error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.GatewayId'.
error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "vpc_endpoint_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.VpcEndpointId'.
error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "vpc_peering_connection_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.VpcPeeringConnectionId'.
error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "carrier_gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.CarrierGatewayId'.
error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "local_gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.LocalGatewayId'.
error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "nat_gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.NatGatewayId'.
error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "network_interface_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.NetworkInterfaceId'.
error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "transit_gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.TransitGatewayId'.
error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "instance_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.InstanceId'.
error: Preview failed: one or more inputs failed to validate
Browsing google for the error leads me to a number of threads talking about legacy Terraform v0.12 such as https://stackoverflow.com/questions/69760888/terraform-inappropriate-value-for-attribute-route
Is this a bug? Should I report it to the aws Classic package maintainers on their github or am I doing something wrong?hundreds-rose-90652
01/18/2022, 10:33 PMproud-engine-17155
01/19/2022, 7:31 AMproud-engine-17155
01/19/2022, 7:32 AMworried-knife-31967
01/19/2022, 9:44 AMbored-table-20691
01/19/2022, 5:48 PMsalmon-account-74572
01/19/2022, 7:02 PMsome-continent-1577
01/19/2022, 7:43 PMmost-lighter-95902
01/20/2022, 5:43 AMpulumi up
fails with an error container XXX cannot be deleted because it cannot be found
(this is not the exact error message) because someone else did pulumi up
on the dev stack and the container names no longer match.magnificent-kitchen-5558
01/20/2022, 8:22 AMhigh-leather-15669
01/20/2022, 1:36 PMcmk
. From the docu, I understand that I first need to create the `databricks-workspace`with `prepare_encryption`set to true
. Once it is created, I need enable encryption
by providing the key, keyvault to the same resource again. That's something I need to do manually, and do two runs of pulumi up
. We are using python
. What's the ideal and better way approach this? Any hints?quick-fall-21011
01/20/2022, 1:57 PM[Output]
attribute but noticed in some cases it saves it as a secret but also as plain text.