bitter-application-91815
08/13/2020, 5:35 PMbitter-application-91815
08/13/2020, 5:35 PMastonishing-quill-88807
08/13/2020, 7:20 PMwet-egg-6347
08/13/2020, 7:29 PMpulumi/random
i then use apply
to write the passwords into a local file (within the kustomize folder). this generates another output (let's call it fileOutput
)
then i need to register the kustomize Directory
... and this is where it gets tricky
my first thought was that i should use the pulumi.DependsOn
option. however DependsOn only accepts resources, and won't accept fileOutput
any tips?bitter-application-91815
08/13/2020, 7:32 PMbitter-application-91815
08/13/2020, 7:32 PMbitter-application-91815
08/13/2020, 7:34 PMbitter-application-91815
08/13/2020, 7:42 PMgentle-hairdresser-12775
08/13/2020, 8:06 PMincalculable-dream-27508
08/13/2020, 8:23 PMastonishing-quill-88807
08/13/2020, 8:26 PMincalculable-dream-27508
08/13/2020, 8:26 PMincalculable-dream-27508
08/13/2020, 8:26 PMgentle-hairdresser-12775
08/13/2020, 8:33 PMworried-engineer-33884
08/13/2020, 9:31 PMbitter-application-91815
08/13/2020, 11:28 PMbitter-application-91815
08/13/2020, 11:28 PMlittle-cartoon-10569
08/13/2020, 11:42 PMlittle-cartoon-10569
08/14/2020, 12:27 AMlittle-cartoon-10569
08/14/2020, 4:31 AMbucket-owner-full-control
issue from a previous thread) while still using the correct profile for creating resources.
When I change from using the default provider to using a provider with the same configuration, Pulumi wants to recreate all my resources. I don't want that (don't delete my RDS and AD!). Can I either
- get the default provider and explicitly use it when appropriate, or
- ignore the change in provider, or
- change the way I'm creating my new-explicit-but-same-as-default provider so that Pulumi doesn't register a difference?kind-mechanic-53546
08/14/2020, 5:23 AMpolite-student-92901
08/14/2020, 5:46 AMtriggerTopic
?helpful-processor-86468
08/14/2020, 1:05 PMagreeable-alligator-68718
08/14/2020, 2:40 PMmillions-furniture-75402
08/14/2020, 5:28 PM.pulumi/ci.json
work when you have multiple projects in a single repository? Is there a ci.json reference/spec?stocky-leather-49710
08/14/2020, 7:45 PMpodAssumeRolePolicyDocument = JsonConvert.SerializeObject(new
{
Version = "2012-10-17",
Statement = new dynamic[]
{
new
{
Action = "sts:AssumeRole",
Principal = new
{
Service = "<http://ec2.amazonaws.com|ec2.amazonaws.com>"
},
Effect = "Allow",
Sid = ""
},
new
{
Sid = "",
Effect = "Allow",
Principal = new
{
AWS = Output.Create(eksNodeGroupRole).Apply(x => x.Arn.ToString())
},
Action = "sts:AssumeRole"
}
}
});
stocky-leather-49710
08/14/2020, 7:45 PMOutput.Create(eksNodeGroupRole).Apply(x => x.Arn.ToString()
just produces an empty stringagreeable-school-57203
08/14/2020, 7:48 PMagreeable-school-57203
08/14/2020, 8:22 PMdamp-secretary-81951
08/15/2020, 12:02 AMpulumi up
aws:cloudformation:Stack (hello-autoscaling-group):
error: 1 error occurred:
* creating urn:pulumi:dev::pulumi-quickstart::awsx:x:ecs:Cluster$awsx:x:autoscaling:AutoScalingGroup$aws:cloudformation/stack:Stack::hello-autoscaling-group: ROLLBACK_COMPLETE: ["The following resource(s) failed to create: [Instances]. . Rollback requested by user." "Property AvailabilityZones cannot be empty."]
Here’s the relevant code:
const name = "hello";
const vpc = awsx.ec2.Vpc.getDefault();
const cluster = new Cluster(`${name}-cluster`, { vpc });
const asg = cluster.createAutoScalingGroup(`${name}-autoscaling-group`, {
templateParameters: { minSize: 2, maxSize: 10 },
launchConfigurationArgs: { instanceType: "t2.micro" },
});
Any idea what’s going on? I’m trying to just use us-east-1
for everything to keep things simple. Thanks!