white-balloon-205
12/17/2019, 6:37 PMelegant-dress-88912
12/19/2019, 6:27 AMeks.createManagedNodeGroup()
pulumi wants to replace resource and fails with error "ResourceInUseException: NodeGroup already exists with name ...".
I guess correct way for this should be generating unique node group name during deploy/replacement, but currently https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/eks/#createManagedNodeGroup requires nodeGroupName
to be specifiedelegant-dress-88912
12/19/2019, 6:29 AM@pulumi/random
as suffix, but not sure how can I make pulumi to regenerate it each time managednodegroup wants new resourcebreezy-butcher-78604
12/20/2019, 8:09 AMaws.iam.RolePolicy
and I want to refer to resources in the same AWS account that Pulumi won’t be aware of. for example, i want to do something like this
const taskPolicy = new aws.iam.RolePolicy("flow-log-service-policy", {
role: taskRole.id,
policy: {
Version: "2012-10-17",
Statement: [
{
Effect: "Allow",
Action: [
"logs:CreateLogStream",
"logs:PutLogEvents"
],
Resource: `arn:aws:logs:${pulumi.getAwsRegion}:${pulumi.getAwsAccountId}:log-group:my-log-group:*`
}
]
}
});
bright-orange-69401
12/22/2019, 1:35 AMminiature-microphone-92266
12/23/2019, 4:13 PMSecurityGroupRule.ingress("http",
appsg,
lbsg,
new awsx.ec2.TcpPorts(80));
I'm getting "Type 'SecurityGroup' has no properties in common with type 'SecurityGroupRuleLocation'."flat-insurance-25294
12/23/2019, 11:31 PMgetZone()
bumpy-restaurant-1466
12/26/2019, 1:40 AMawsx.ec2.Vpc
with 4 different subnet groups (private, public, db, redis). In order for them to show in the console as sensible name you can include tags: { Name: "db" }
for each subnet, however unfortunately that results in a subnet group’s subnets having the same name regardless of what az they are in. Instead I’d like to have their names follow the format example-name-az
or example-name-number
, eg example-db-us-west-2
or example-db-2
. How can I achieve this without needing to specify each az subnet one at a time?orange-australia-91292
12/27/2019, 7:06 PMhandsome-truck-95168
12/27/2019, 7:50 PMflat-insurance-25294
12/28/2019, 11:06 PMflat-insurance-25294
12/28/2019, 11:07 PMorange-australia-91292
12/29/2019, 9:26 AMget()
a resource that is in another region than the one I’m working in?
Example: My region is set to eu-west-1: aws:region: eu-west-1
. I’m trying to
import pulumi
from pulumi_aws import s3
s3.Bucket.get("my-bucket", "my-bucket", region="eu-central-1")
and I get
Bucket (my-bucket): BucketRegionError: incorrect region, the bucket is not in 'eu-west-1' region at endpoint ''
status code: 301, request id: , host id:
orange-australia-91292
12/29/2019, 9:27 AMregion
argument or not, the result is the same. Is this a bug, or am I missing something again?orange-australia-91292
12/29/2019, 9:29 AMflat-insurance-25294
12/29/2019, 10:15 AMorange-australia-91292
12/29/2019, 10:46 AMflat-insurance-25294
12/29/2019, 10:57 AMflat-insurance-25294
12/29/2019, 10:57 AMorange-australia-91292
12/29/2019, 11:09 AMorange-australia-91292
12/29/2019, 11:14 AMflat-insurance-25294
12/29/2019, 2:24 PMflat-insurance-25294
12/29/2019, 2:44 PMflat-insurance-25294
12/29/2019, 2:45 PMflat-insurance-25294
12/29/2019, 2:59 PMfuture-yak-43516
12/29/2019, 5:05 PMworried-engineer-33884
12/30/2019, 8:43 PMpulumi up
— is this new behavior?worried-engineer-33884
12/30/2019, 11:03 PMflat-insurance-25294
01/03/2020, 10:45 AMarn:aws:dynamodb:us-east-2:123456789012:table/Books
somehow? When creating a dynamodb for creating a Policy to give access to a group?flat-insurance-25294
01/03/2020, 10:47 AMflat-insurance-25294
01/03/2020, 10:47 AM