brave-salesmen-42327
01/15/2020, 7:51 PMosProfile: {
customData: `#!/bin/bash\n
echo "${someConfigValue}"`
}
It does not change the resource according to pulumi cli. Reports All Resources Unchanged, no update or destroy re-create happens.
Changing something like
vmSize: "SomeOtherSize"
works fine, registers as a change and updates the vm resource.gifted-beach-2614
01/15/2020, 9:01 PMbusy-dusk-74339
01/16/2020, 12:50 AMbusy-dusk-74339
01/16/2020, 12:51 AMcareful-market-30508
01/16/2020, 3:22 AMlate-printer-99022
01/16/2020, 4:16 AMlate-printer-99022
01/16/2020, 12:01 PMlate-printer-99022
01/16/2020, 7:03 PMpulumi up
showed me following update.
pulumi:pulumi:Stack: (same)
[urn=urn:pulumi:prod::syngenta-platform::pulumi:pulumi:Stack::syngenta-platform-prod]
~ kubernetes:<http://networking.k8s.io/v1beta1:Ingress|networking.k8s.io/v1beta1:Ingress>: (update)
[id=syngenta-platform/syngenta-platform]
[urn=urn:pulumi:prod::syngenta-platform::kubernetes:<http://networking.k8s.io/v1beta1:Ingress::syngenta-platform|networking.k8s.io/v1beta1:Ingress::syngenta-platform>]
[provider=urn:pulumi:prod::syngenta-platform::eks:index:Cluster$pulumi:providers:kubernetes::syngenta-platform-provider::bb6ecf4e-2c78-4f12-8c8f-0f1b8d4ce3a7]
~ spec: {
~ rules: [
~ [0]: {
~ http: {
~ paths: [
~ [1]: {
~ path: "/ngnix/*" => "/nginx/*"
}
]
}
}
]
}
Resources:
~ 1 updated
63 unchanged
Duration: 1m3s
But when I went to aws console, the path is not updated in Target Group.
did I missed something?powerful-football-81694
01/16/2020, 8:40 PMpowerful-football-81694
01/16/2020, 8:59 PMinit
command in the dropdown, but executing the pipeline yields:
Error: unknown command "init" for "pulumi"
Did you mean this?
new
Run 'pulumi --help' for usage.
worried-engineer-33884
01/16/2020, 9:40 PMmake
, but it seems that you need to npm install
first, but that doesn't work because version in package.json is set to ${VERSION}
. I don't want to hack around too much with this — is there an updated version of development spinup instructions?
https://github.com/pulumi/pulumi/tree/master/sdk/nodejs#building-and-testingflat-insurance-25294
01/16/2020, 11:33 PMif (config.isProduction == false) {
export const rdsPassword = rds.masterPassword
}
Like that wouldn’t work.helpful-kitchen-78641
01/16/2020, 11:40 PMus-west-2
). I am creating a certificate in us-east-1
because I need to use it as part of a cloudfront distribution, which requires the cert to live there.
// [...]
const regionProvider = new aws.Provider('us-east-provider', {region: 'us-east-1'});
const certCertificate = new aws.acm.Certificate('cert', {
domainName: '<http://dashboard.mydomain.com|dashboard.mydomain.com>',
subjectAlternativeNames: [
'*.<http://dashboard.mydomain.com|dashboard.mydomain.com>',
],
validationMethod: 'DNS',
tags,
}, {provider: regionProvider});
const certValidation = new aws.route53.Record('certValidation', {
name: certCertificate.domainValidationOptions[0].resourceRecordName,
records: [certCertificate.domainValidationOptions[0].resourceRecordValue],
ttl: 300,
type: certCertificate.domainValidationOptions[0].resourceRecordType,
zoneId: dashboardR53Zone.id,
});
const certCertificateValidation = new aws.acm.CertificateValidation('cert', {
certificateArn: certCertificate.arn,
validationRecordFqdns: [
certValidation.fqdn,
certValidation.fqdn, // both entries use the same value/name per the AWS console
],
});
After running pulumi up
I receive the following error:
Diagnostics:
aws:acm:CertificateValidation (cert):
error: Error describing certificate: ResourceNotFoundException: Could not find certificate arn:aws:acm:us-east-1:[REDACTED]:certificate/60c[REDACTED]df9d9.
status code: 400, request id: 4c00[REDACTED]aef6
I can see the certificate with that ARN in the AWS console, so I'm not sure how to proceedhelpful-kitchen-78641
01/16/2020, 11:42 PMhelpful-kitchen-78641
01/17/2020, 12:04 AM{provider: regionProvider}
in the validation 🤦♂️adventurous-vase-24423
01/17/2020, 11:19 AMpowerful-football-81694
01/17/2020, 1:22 PMcommand: stack
and options: init $(StackName)
in the YAML.
However, the Pulumi@1
task has a mandatory stack
parameter, and the task always tries to select that stack the first thing it does, before it proceeds to execute the actual command, which of course results in an error because the stack does not yet exist.busy-dusk-74339
01/17/2020, 2:30 PMbusy-dusk-74339
01/17/2020, 2:32 PMpulumi preview --diff
it highlights securityGroups
as having changes, but the contents of the object are identical to the instance above that it wants to delete …busy-dusk-74339
01/17/2020, 2:33 PM- aws:ec2/instance:Instance: (delete)
[id=i-0b024d1ad4cb75dba]
[urn=urn:pulumi:dev::talend_poc::aws:ec2/instance:Instance::talend_poc_instance]
[provider=urn:pulumi:dev::talend_poc::pulumi:providers:aws::default_1_8_0::90aafd96-3c4a-4649-9def-fb795391f334]
ami : "ami-04bfa3d65c8508b02"
disableApiTermination: true
getPasswordData : false
iamInstanceProfile : "talend_poc_profile-1f0f54b"
instanceType : "m4.xlarge"
keyName : "ops"
rootBlockDevice : {
deleteOnTermination: true
volumeSize : 300
}
securityGroups : [
[0]: "sg-095e0af0371379410"
[1]: "sg-078d2ef15a737ac03"
]
sourceDestCheck : true
subnetId : "subnet-08d1f41a5bd97f622"
tags : {
Name : "talend-poc"
application: "talend-poc"
}
userData : "IyEvYmluL2Jhc2gKCnN..."
busy-dusk-74339
01/17/2020, 2:33 PMpulumi:pulumi:Stack: (same)
[urn=urn:pulumi:dev::talend_poc::pulumi:pulumi:Stack::talend_poc-dev]
> pulumi:pulumi:StackReference: (read)
[id=PLOS/iam/dev]
[urn=urn:pulumi:dev::talend_poc::pulumi:pulumi:StackReference::PLOS/iam/dev]
name: "PLOS/iam/dev" +-aws:ec2/instance:Instance: (replace)
[id=i-099b9ef2206465ee3]
[urn=urn:pulumi:dev::talend_poc::aws:ec2/instance:Instance::talend_poc_instance]
[provider: urn:pulumi:dev::talend_poc::pulumi:providers:aws::default_1_8_0::90aafd96-3c4a-4649-9def-fb795391f334 => urn:pulumi:dev::talend_poc::pulumi:providers:aws::default_1_18_0::output<string>]
~ securityGroups: [
+ [0]: "sg-095e0af0371379410"
+ [1]: "sg-078d2ef15a737ac03"
]
helpful-kitchen-78641
01/17/2020, 7:44 PMPulumi.stack.yaml
config:
aws:profile: StagingAdmin
and in my index.ts
code I would like to do something like:
const prof = config.require('aws:profile');
helpful-kitchen-78641
01/17/2020, 7:50 PMconst prof = aws.config.profile;
busy-dusk-74339
01/17/2020, 10:39 PMbusy-dusk-74339
01/17/2020, 10:40 PMloud-nest-15724
01/18/2020, 1:41 PMmysterious-egg-7415
01/18/2020, 4:27 PMsteep-toddler-94095
01/19/2020, 3:17 AMbuild.cacheFrom
parameter does not seem to allow me to use an image with a different name as the cache source. It's different from how docker --cache-from
works. Am I out of luck on this if i want to use another image for the build cache?broad-dog-22463
01/20/2020, 10:50 AMconst providers: {[key: string]: aws.Provider} = {
"us-east-1": new aws.Provider("us-east-1", {region: "us-east-1"}),
"us-east-2": new aws.Provider("us-east-2", {region: "us-east-2"}),
"us-west-2": new aws.Provider("us-west-2", {region: "us-west-2"})
};
for (const providerKey of Object.keys(providers)) {
const provider = providers[providerKey];
const lambda = new aws.lambda.Function(`my-lambda-function-${providerKey}`, {
name: "lambda-for-account-cleanup",
runtime: aws.lambda.Go1dxRuntime,
timeout: 900,
role: iamRoleArn,
handler: "main",
code: new pulumi.asset.FileArchive("../deployment.zip"),
environment: {
variables: {
"DESTROY_ENABLED": "false"
}
},
tags: {
"Owner": "Stack72",
"Purpose": "AccountCleanup",
}
}, {provider: provider});
}
limited-rainbow-51650
01/20/2020, 11:09 AM