jolly-camera-35709
10/20/2020, 5:48 AMbitter-application-91815
10/20/2020, 1:36 PMbitter-application-91815
10/20/2020, 1:36 PMbitter-application-91815
10/20/2020, 1:36 PMaws:ec2:RouteTable (axiom-cloud-private-subnet-3-routetable-staging-g):
error: 1 error occurred:
* updating urn:pulumi:axiom-cloud::staging::aws:ec2/routeTable:RouteTable::axiom-cloud-private-subnet-3-routetable-staging-g: Error creating route: RouteAlreadyExists: The route identified by 0.0.0.0/0 already exists.
status code: 400, request id: c7800e9a-2e62-4efb-ad81-34b27f11c628
bitter-application-91815
10/20/2020, 1:37 PMbitter-application-91815
10/20/2020, 1:37 PMbitter-application-91815
10/20/2020, 1:40 PMView Live: <https://app.pulumi.com/axiom/staging/axiom-cloud/previews/a92a225e-8e64-40a2-b968-08f187e38f2f>
Type Name Plan Info
pulumi:pulumi:Stack staging-axiom-cloud
~ ├─ aws:ec2:RouteTable axiom-cloud-private-subnet-3-routetable-staging-g update [diff: ~routes]
~ ├─ aws:ec2:RouteTable axiom-cloud-private-subnet-1-routetable-staging-g update [diff: ~routes]
~ ├─ aws:ec2:RouteTable axiom-cloud-private-subnet-2-routetable-staging-g update [diff: ~routes]
+- ├─ aws:ecs:TaskDefinition monitors-staging-g-ecs-task replace [diff: ~containerDefinitions]
~ ├─ aws:ecs:Service monitors-staging-g-ecs-service update [diff: ~taskDefinition]
└─ kubernetes:<http://helm.sh/v3:Chart|helm.sh/v3:Chart> axiomdb-charts-staging-g
└─ kubernetes:extensions/v1beta1:Ingress axiomdb/axiomdb-ingress 1 warning
Diagnostics:
kubernetes:extensions/v1beta1:Ingress (axiomdb/axiomdb-ingress):
warning: extensions/v1beta1/Ingress is deprecated by <http://networking.k8s.io/v1beta1/Ingress|networking.k8s.io/v1beta1/Ingress> and not supported by Kubernetes v1.20+ clusters.
Do you want to perform this update? yes
Updating (axiom/axiom-cloud)
View Live: <https://app.pulumi.com/axiom/staging/axiom-cloud/updates/67>
Type Name Status Info
pulumi:pulumi:Stack staging-axiom-cloud **failed** 1 error
~ ├─ aws:ec2:RouteTable axiom-cloud-private-subnet-2-routetable-staging-g updated [diff: ~routes]
~ ├─ aws:ec2:RouteTable axiom-cloud-private-subnet-3-routetable-staging-g **updating failed** [diff: ~routes]; 1 error
~ └─ aws:ec2:RouteTable axiom-cloud-private-subnet-1-routetable-staging-g updated [diff: ~routes]
bitter-application-91815
10/20/2020, 1:40 PMbrash-student-27683
10/20/2020, 2:49 PMvpc1 = new awsx.ec2.Vpc(..)
vpc2 = new awsx.ec2.Vpc(..)
new aws.ec2.VpcPeeringConnection(..)
now that the peering is set up, I need to add the route table entries to both the vpc’s route tables. But with crosswalk, these route tables are internally created for me. How do I access these route tables to add a new route to them? (to point the vpcs to each other)careful-nail-88325
10/20/2020, 4:29 PMpulumi.runtime.isDryRun()
to determine whether a preview or update is being executed and assuming the corresponding role. Unfortunately, the change in the provider also affects the state of my stack. Is there a recommended way to do this? Currently, I think I'm going to have to abandon the assumeRole functionality of the AWS provider and assume the role with the AWS CLI in advance before executing preview or update.tall-needle-56640
10/20/2020, 4:32 PM> pulumi up
Previewing update (dev)
Type Name Plan
pulumipulumiStack PulumiPort-dev
+ ├─ azureappserviceFunctionApp app create
- └─ azureappserviceFunctionApp test20201910func delete
Resources:
+ 1 to create
- 1 to delete
2 changes. 5 unchanged
Do you want to perform this update? yes
Updating (dev)
Type Name Status Info
pulumipulumiStack PulumiPort-dev failed 1 error
+ └─ azureappserviceFunctionApp app creating failed 1 error
Diagnostics:
azureappserviceFunctionApp (app):
error: web.AppsClient#CreateOrUpdate: Failure sending request: StatusCode=404 -- Original Error: Code="NotFound" Message="Cannot find ServerFarm with name test20201910-aspa9aae18b." Details=[{"Message":"Cannot find ServerFarm with name test20201910-aspa9aae18b."},{"Code":"NotFound"},{"ErrorEntity":{"Code":"NotFound","ExtendedCode":"51004","Message":"Cannot find ServerFarm with name test20201910-aspa9aae18b.","MessageTemplate":"Cannot find {0} with name {1}.","Parameters":["ServerFarm","test20201910-aspa9aae18b"]}}]
worried-queen-62794
10/20/2020, 9:50 PMaws.ec2.get_network_interface
which doesn't define it's properties as inputs but rather the raw types, i.e. str?worried-queen-62794
10/20/2020, 10:39 PMworried-queen-62794
10/20/2020, 10:43 PMlittle-cartoon-10569
10/20/2020, 11:00 PMbrief-spoon-92183
10/21/2020, 11:37 AMitself
? (here's an example)
I'm creating an Elastic Search Domain, and the accessPolicies
requires a Resource
ARN, which I don't know how to construct to match the domain ID (see screenshot):billions-forest-38488
10/21/2020, 12:52 PMpulumi destroy
command, for example: only when destroying a stack, I'd also like to run a bit of code to cleanup some third-party resources... in this case, cleanup a Logentries logset/log - thanks! (I'm using Python if that helps..)high-morning-17948
10/21/2020, 9:26 PMaws:batch:JobDefinition (booksloth-import-dev-importLauncher-job-definition):
error: 1 error occurred:
* : Error executing request, Exception : The validated object is null, RequestId: 3b39ec6f-fcaf-4ea9-bb13-52991d45c6c1
status code: 400, request id: 3b39ec6f-fcaf-4ea9-bb13-52991d45c6c1 "booksloth-import-dev-importLauncher-job-definition"
Any suggestion of what I'm missing for the creation.
Here's the code snippet for creating the resource
/**
* Define Job definition Container properties
* See {@link <https://docs.aws.amazon.com/batch/latest/APIReference/API_ContainerProperties.html> | AWSContainerProperties}
* for reference
*/
const containerProperties = jobRole.arn.apply(arn => {
return JSON.stringify({
image: imgName,
command: ['node', 'index.js'],
memory: 2000, // in MiB
jobRoleArn: arn,
environment: [
{ name: 'NODE_ENV', value: config.stage },
{ name: 'APP_VARS', value: appVars },
{ name: 'BOOKSLOTH_API_VARS', value: bookslothApiVars },
],
})
});
console.log({ containerProperties })
/**
* Create Batch Job Defintion
*/
const jobDefinition = new aws.batch.JobDefinition(`${config.prefix}-${serviceName}-job-definition`, {
name: `${config.prefix}-${serviceName}-job-definition`,
type: 'container',
containerProperties,
retryStrategy: { attempts: 3 }
}, {
dependsOn: [
jobRoleECSPolicyAttachment,
jobRoleBookQueueAccess,
jobRoleUserbooklistQueueAccess
]
});
famous-area-1376
10/22/2020, 6:25 AMjolly-camera-35709
10/22/2020, 6:52 AMjolly-camera-35709
10/22/2020, 6:54 AMjolly-camera-35709
10/22/2020, 6:55 AMjolly-camera-35709
10/22/2020, 6:57 AMjolly-camera-35709
10/22/2020, 6:58 AMbreezy-butcher-78604
10/22/2020, 3:15 PMpulumi login
again just logs me in with the existing account (my work one)brief-spoon-92183
10/22/2020, 5:02 PMAWSServiceRoleForAmazonElasticsearchService
?
The error looks like this:
Error creating service-linked role with name <http://es.amazonaws.com|es.amazonaws.com>: InvalidInput: Service role name AWSServiceRoleForAmazonElasticsearchService has been taken in this account, please try a different suffix.
I followed the VPC based ES
example in the docs.
Any ideas how to either reuse the existing role, or create a new one for each ES domain?
Thanksmany-spring-73557
10/22/2020, 6:43 PMgcp.cloudrun.DomainMapping
. Every time I pulumi up
, it says there’s a change to metadata annotations serving.knative.dev/creator
and serving.knative.dev/lastModifier
which match my username. This results in GCP destroying and re-creating the DomainMapping each time, which I don’t want. How can I keep this from happening?
One thing I’ve found is I can ignoreChanges: ["metadata.annotations"]
which is pretty good - but I do have some annotations that should actually get picked up by pulumi. I haven’t found a way to target those specific annotations that I want to ignorebreezy-butcher-78604
10/23/2020, 4:51 AMjolly-camera-35709
10/23/2020, 6:14 AMjolly-camera-35709
10/23/2020, 6:14 AM