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 AMjolly-camera-35709
10/23/2020, 6:16 AMjolly-camera-35709
10/23/2020, 6:16 AMenvironment_variables=[
'BRANCH_NAME': 'master',
]
nutritious-shampoo-16116
10/23/2020, 8:14 AMnutritious-shampoo-16116
10/23/2020, 8:16 AMnutritious-shampoo-16116
10/23/2020, 8:17 AMnutritious-shampoo-16116
10/23/2020, 8:54 AM:
is not valid and the provider cannot be instantiated properly, the error message in this case is very misleadingcolossal-monkey-98692
10/23/2020, 3:31 PMbitter-application-91815
10/23/2020, 5:42 PMalert-beard-9601
10/23/2020, 8:21 PMhigh-morning-17948
10/23/2020, 8:36 PM<docker://pulumi/actions>
had any updates because now my Github Actions deployment is failing because it doesn't find Pulumi.yml
. I haven't changed my scripts recently and if I run it locally with pulumi up
it works has expected.steep-toddler-98503
10/23/2020, 9:42 PMsteep-toddler-98503
10/23/2020, 9:42 PMbillowy-army-68599
10/23/2020, 9:52 PMsteep-toddler-98503
10/24/2020, 6:54 PM