worried-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!refined-teacher-35628
08/15/2020, 8:53 AMconst default_vpc = awsx.ec2.Vpc.getDefault();
console.log(default_vpc.internetGateway.id)
kind-address-14510
08/15/2020, 2:24 PM'resourceGroupName' is not defined
for Azure ARM template deployment
File "./__main__.py", line 23, in <module>
resourceGroupName: resource_group.name,
NameError: name 'resourceGroupName' is not defined
error: an unhandled error occurred: Program exited with non-zero exit code: 1
part of code here, not sure where to look for TemplateDeployment
docs , can't see them in API reference
armDeployment = azure.core.TemplateDeployment("test-dep", {
resourceGroupName: resource_group.name,
templateBody: JSON.stringify(content),
parameters: {
"storageAccountType": "Standard_GRS",
},
deploymentMode: "Incremental",
})
little-cartoon-10569
08/16/2020, 11:25 PMpulumi refresh
wants to delete all my NACLs and rules from state, and not update anything. That will leave a pile of good(ish) NACLs and rules in AWS, and Pulumi won't be able to manage them.
How can I recover? I can't see anything in pulumi stack --help
or pulumi state --help
that meets my needs. There's a few options that would help if they were possible: updating the state to match reality, importing reality from AWS into the state, or deleting the NACs and rules from AWS so that reality matches state. Which is the best, and how do I do it?little-cartoon-10569
08/17/2020, 1:10 AM{ import: 'pcx-xyzabc123' }
opt to the ComponentResource constructor instead of to the aws.ec2.VpcPeeringConnection
constructor. This failed because now it's trying to import all resources with the same id (because the opts that I pass to my ComponentResource gets passed to all the nested resources).
So I fixed that. Now when I run preview, it says it'll import my VpcPeeringConnection fine, but it's still trying to import the other resources! Even when I remove the import:
altogether, it's still trying to import! The specific error message is like this:
error: Preview failed: importing pcx-075eac9319f99ebd2: unexpected format of ID ("pcx-xyzabc123"), expected NETWORK_ACL_ID:RULE_NUMBER:PROTOCOL:EGRESS
little-cartoon-10569
08/17/2020, 3:03 AMconst provider = new aws.Provider('x", { region: 'us-east-1', profile: 'assumed-role-in-acct-FOO'});
const identity = aws.getCallerIdentity({ provider: provider});
The returned identity
is the one from the default provider. I expect to see a different arn, accountId and userId in there. Am I doing something wrong?great-optician-69584
08/17/2020, 5:45 AMsquare-rose-64819
08/17/2020, 12:10 PMlittle-wolf-72041
08/17/2020, 1:59 PMgray-lawyer-89054
08/17/2020, 2:13 PMpulumi logs
command. https://www.pulumi.com/blog/unified-logs-with-pulumi-logs/ In this article you mentioned that K8s will be also supported. Do you have some idea when this might happen?brief-spoon-92183
08/17/2020, 2:14 PMrollback
in your docs. Does Pulumi support rollback on failed deploys, and if not, do you plan to support it at some point in the future? Thanks!prehistoric-arm-87050
08/17/2020, 3:51 PMdamp-secretary-81951
08/17/2020, 4:06 PMFargateTaskDefinition
is used twice (instead of EC2TaskDefinition
), same goes for FargateService
, which is used twice instead of EC2Service
.
https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/ecs/#task-definitions
https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/ecs/#services
Overall the docs have been very helpful. Thanks for updating!busy-iron-87492
08/17/2020, 4:36 PMmillions-dog-5491
08/17/2020, 5:02 PMmillions-dog-5491
08/17/2020, 5:02 PM