helpful-knife-18557
07/09/2021, 3:42 PMnumerous-fountain-44949
07/09/2021, 4:06 PMdamp-school-17708
07/09/2021, 4:56 PMCould not include required dependency '@aws-sdk/client-codepipeline' in '/Users/toni/code/link/infrastructure'.
I am not entirely sure why it would happen, while the same stack used to use '@aws-sdk/client-codebuild'
The code using it it's an 'inline lambda' done with new awsx.apigateway.API
How is that possible? there's a closed github issue but it doesn't seem related, what could be the culprit? Do I need to define a 'standard' lambda to circumvent this?
Latest versions of all packages, just updated. Not sure if it matters but using a monorepo structure, with this dependency/stack inside a folder.gray-belgium-81846
07/11/2021, 6:31 PMtaskDefinition.run({cluster})
However, when I run pulumi up
I get:
error: Error: Cannot call '.get' during update or preview.
To manipulate the value of this Output, use '.apply' instead.
at Proxy.get (.../node_modules/@pulumi/pulumi/output.js:173:15)
at FargateTaskDefinition.run (.../node_modules/@pulumi/ecs/taskDefinition.ts:229:39)
Any ideas? I think I need to wrap this is an async function somehow, but some guidance would be appreciated. The sample code shows this working in response to an API gateway handler, but I’d like it to execute when the pulumi program runs.stocky-parrot-75654
07/12/2021, 12:15 PM${environmentName}-waf-cf-default-web-geo-rule
,
priority: 1,
action: {
allow: {}
},
statement: {
orStatement: {
statements: [{
geoMatchStatement: {
countryCodes: [
“US”,
“CA”
]
},
ipSetReferenceStatement: {
arn: cfIpSetWhiteList.arn
}
}]
}
},
visibilityConfig: {
cloudwatchMetricsEnabled: false,
metricName: ${environmentName}-waf-cf-default-web-geo-rule-metric
,
sampledRequestsEnabled: false
}
}green-intern-27665
07/12/2021, 2:56 PMdamp-school-17708
07/13/2021, 9:09 AMlittle-market-63455
07/13/2021, 12:24 PMaws.lb.listener
?
Has anyone seen this behavior before?
Keeps saying You cannot specify a target group weight on load balancers of type 'network'
and my group definition looks like:
const fileUploadListener = new aws.lb.Listener('fileUploadListener',
{
defaultActions: [
{
type: 'forward',
forward: {
targetGroups: [{ arn: fileUploadTargetGroup.arn }],
},
},
],
loadBalancerArn: // some ARN,
port: 8084,
protocol: 'TCP',
},
)
many-salesmen-89069
07/13/2021, 12:43 PMError creating DB Instance: InvalidDBInstanceState: Automated backups are not enabled for this database instance. To enable automated backups, use ModifyDBInstance to set the backup retention period to a non-zero value.
This is my code:
const replicaDbSubnets = new aws.rds.SubnetGroup("replica-db-subnets", {
subnetIds: vpc.publicSubnetIds,
});
const isolatedDbReplica = new aws.rds.Instance(`${name}-isolated-db-replica`, {
instanceClass: "db.t2.micro",
allocatedStorage: 10,
dbSubnetGroupName: replicaDbSubnets.name,
vpcSecurityGroupIds: [isolatedReplicaSg.id],
skipFinalSnapshot: true,
publiclyAccessible: true,
replicateSourceDb: isolatedDb.identifier,
backupRetentionPeriod: 0
});
My understanding is that backups should be only enabled for the source db?green-intern-27665
07/13/2021, 1:11 PMpulumi up
everything works nice. I automatically upload the docker image to the ERS and I have a new container definition each time I perform a pulumi up
. My issue is that in spite the container_definition
is new inside the task, tasks are not updated and in consequence the services are not updated. Any idea about how to force the service update forcing a rolling update in the service??fancy-flower-77794
07/13/2021, 1:44 PMrefined-terabyte-65361
07/13/2021, 6:52 PMimport * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
const foo = new aws.ecr.Repository("foo", {
imageScanningConfiguration: {
scanOnPush: true,
},
imageTagMutability: "MUTABLE",
});
but when my repo gets created i am expecting name to be foo but it creates repo with random id foo-719afa7
how to create repo without random id ?purple-orange-91853
07/13/2021, 9:12 PMpulumi:providers:aws default_4_12_0 error: no resource plugin 'aws-v4.12.0' found in the workspace or on your $PATH, install the plugin using pulumi plugin install resource aws v4.12.0
. Above that I see that we have installed v4.11.0 as defined in our config which worked late last week when I testing against this method.
Executing command: pulumi plugin install resource aws v4.11.0
[resource plugin aws-4.11.0] installing
Downloading plugin: 75.91 MiB / 75.91 MiB 100.00% 1s
How do we avoid this and/or is it possible to have the pulumi plugin install
command always pull the latest version rather than manually specifying a version on run time?
The pipeline is pulling the pulumi/pulumi:3.6.1 docker image to run in.
Pulling image pulumi/pulumi:v3.6.1
Digest: sha256:28c72d280cf89401cbc5600be57d15372c43483702a170edcdb772907288f6f1
Status: Image is up to date for pulumi/pulumi:v3.6.1
victorious-helmet-11068
07/14/2021, 12:17 PMvictorious-helmet-11068
07/14/2021, 12:18 PMvictorious-helmet-11068
07/14/2021, 12:18 PMvictorious-helmet-11068
07/14/2021, 12:19 PMvictorious-helmet-11068
07/14/2021, 12:19 PMvictorious-helmet-11068
07/14/2021, 12:19 PMproud-easter-54321
07/14/2021, 1:32 PMhelpful-knife-18557
07/15/2021, 4:01 PMbroad-hairdresser-1495
07/16/2021, 10:37 AMaws.ec2.get_instance
:
import pulumi_aws as aws
imported_instance = aws.ec2.get_instance(
#instance_id="i-08e44dd991ede45a8",
filters=[{'Name': 'tag:Name', 'Values': ["my_ec2_instanceName"]}])
print("::::::::instance_id")
print(imported_instance.instance_id)
print("::::::::id")
print(imported_instance.id)
Please note that results differ:
::::::::instance_id
None //getting None when not using 'instance_id="i-08e44dd991ede45a8"
::::::::id
i-08e44dd991ede45a8
and when using instance_id="i-08e44dd991ede45a8"
Results are:
::::::::instance_id
i-08e44dd991ede45a8 //getting 'i-08e44dd991ede45a8' when using 'instance_id="i-08e44dd991ede45a8"
::::::::id
i-08e44dd991ede45a8
proud-pizza-80589
07/16/2021, 11:04 AMboundless-telephone-75738
07/16/2021, 2:19 PMconst pgProvider = (db: rds.Instance, pw: string) => {
return new pg.Provider(`${name}-db-provider`, {
port: db.port,
host: db.address,
password: pw,
username: db.username,
superuser: true
});
}
but that causes pulumi to try to connect to the rds.Instance private ip. and I end up with error: error detecting capabilities: error PostgreSQL version: dial tcp: lookup <privateip>
when trying to define a role.
Is there a way to use aws.rds to create roles and databases in addition to the initialDatabase created when using
aws.rds.Instance('name', config)
From the docs it's not clear to me how to do this. Which is the reason why I moved to the postgresql package, and tried to define a provider to tell it about my rds instance.
I found https://www.pulumi.com/blog/managing-your-mysql-databases-with-pulumi/ for mysql, but the pg.Provider does not accept an endpoint, I tried using endpoint for the host property, but that causes a double :PORT:PORT
breezy-lunch-69325
07/16/2021, 4:36 PM${name}-{id}
breezy-lunch-69325
07/16/2021, 4:37 PMawsx.ecs.Image.fromPath("test", "./")
where test
is a repo i already defined with custom rules. Anyone else experience this? Not sure if it's a bug or i'm doing something wrongbest-train-86003
07/18/2021, 4:09 PMbest-train-86003
07/18/2021, 4:11 PMpulumi preview -r
and i see it get stuck for some reason. How can i know what resource makes it stuck? how do i fix this issue?ripe-shampoo-80285
07/18/2021, 9:29 PMripe-shampoo-80285
07/18/2021, 10:14 PM\"Resource\": \"arn:aws:sqs:*:*:s3-event-notification-queue\",
to this, the error went away:
\"Resource\": \"*\",