little-energy-64187
08/19/2019, 4:46 PMconst serviceAccount = new gcp.serviceAccount.Account("example", {
displayName: "example",
accountId: "example-service-account",
project: "project"
}, { import: "projects/project/serviceAccounts/example-service-account@project.iam.gserviceaccount.com" })
const roles = new gcp.projects.IAMCustomRole("example", {
roleId: "example",
title: "example",
description: "example roles",
permissions: [
'compute.addresses.list',
'compute.instances.addAccessConfig',
'compute.instances.deleteAccessConfig',
'compute.instances.get',
'compute.instances.list',
'compute.projects.get',
'container.clusters.get',
'container.clusters.list',
'resourcemanager.projects.get',
'compute.networks.useExternalIp',
'compute.subnetworks.useExternalIp',
'compute.addresses.use',
]
}, { import: "projects/project/roles/example" })
const examplePolicyBinding = new gcp.serviceAccount.IAMBinding("example", {
serviceAccountId: serviceAccount.accountId,
members: ["serviceAccount:example-service-account@project.iam.gserviceaccount.com"],
role: "projects/project/roles/example"
}, { import: "<mailto:example-service-account@project.iam.gserviceaccount.com|example-service-account@project.iam.gserviceaccount.com>" })
policy binding fails with Wrong number of parts to Binding id [example-service-account@project.iam.gserviceaccount.com]; expected 'resource_name role'.
best-xylophone-83824
08/19/2019, 5:07 PMconfig/gke01-london.ts:6:9 - error TS2322: Type '{ machineType: string; preemptible: boolean; }' is not assignable to type '"nodeConfig"'.
6 nodeConfig: {
~~~~~~~~~~
node_modules/@pulumi/gcp/container/nodePool.d.ts:312:14
312 readonly nodeConfig?: pulumi.Input<{
~~~~~~~~~~
The expected type comes from property 'nodeConfig' which is declared here on type 'NodePoolConfigArgs'
all I wanted is to check that provided config matches NodePoolArgs. Everything in 'NodePoolConfigArgs["nodeConfig"]'
is optional, yet even {}
cannot be assigned to it.quick-action-34599
08/19/2019, 9:54 PMquick-action-34599
08/19/2019, 9:55 PMpulumi up -y || pulumi up -y
best-xylophone-83824
08/20/2019, 12:43 PMquick-action-34599
08/20/2019, 2:41 PMquick-action-34599
08/20/2019, 2:41 PMadamant-dress-73325
08/20/2019, 3:58 PMpulumi refresh
.
++aws:ec2/instance:Instance: (create-replacement)
<snip>
~ securityGroups: [
+ [0]: "sg-082e7a6e007b182dc"
]
+-aws:ec2/instance:Instance: (replace)
~ securityGroups: [
+ [0]: "sg-082e7a6e007b182dc"
]
cool-hair-35481
08/20/2019, 6:16 PMbitter-dentist-28132
08/20/2019, 7:11 PMpulumi/pulumi:latest
matches what's latest
in npm?alert-beard-9601
08/20/2019, 9:54 PMbest-xylophone-83824
08/21/2019, 11:08 AM+-gcp:container/cluster:Cluster: (replace) 🔒
[id=gke01-london]
[urn=urn:pulumi:gke01-london::gcp-gke::gcp:container/cluster:Cluster::gke01-london]
[provider=urn:pulumi:gke01-london::gcp-gke::pulumi:providers:gcp::default_1_0_0_beta_1::1a4df25a-af6f-4fda-80df-2c8bd047655a]
+ authenticatorGroupsConfig: {
+ securityGroup: "gke-security-groups@$corp"
}
+ maintenancePolicy : {
+ dailyMaintenanceWindow: {
+ startTime : "01:00"
}
}
+ podSecurityPolicyConfig : {
+ enabled : true
}
best-xylophone-83824
08/21/2019, 12:55 PMResources constructed as children of a component should make sure that their names will be unique across multiple instances of the component. In general, the name of the component instance itself (the name parameter passed in to the component constructor) shoud be used as part of the name of the child resources.
some-doctor-62800
08/21/2019, 2:30 PMpulumi up
run?some-doctor-62800
08/21/2019, 2:31 PMsome-doctor-62800
08/21/2019, 2:31 PMabundant-airplane-93796
08/21/2019, 3:02 PMabundant-airplane-93796
08/21/2019, 3:02 PMincalculable-angle-91273
08/21/2019, 5:28 PMkubernetes:extensions:Deployment (istio-system/istio-pilot):
error: Plan apply failed: 1 error occurred:
* resource istio-system/istio-pilot was successfully created, but the Kubernetes API server reported that it failed to fully initialize or become live: Timeout occurred for 'istio-pilot'
But the api shows 2/2 up. It showed this before the timeout too:
istio-pilot 2/2 2 2 10m
does anyone have any thoughts on how I can further debug this? It appeared to deploy everything fine but pulumi timed out. @gorgeous-egg-16927 maybe?early-intern-90238
08/21/2019, 6:23 PMbrave-angle-33257
08/21/2019, 10:56 PMsubnet_zone_letters:string[] = ['a', 'b', 'c', 'd'];
I want to make sure the other stack uses the same values, so I pass them as an output:
export let vpc_subnet_zone_letters = vpc.subnet_zone_letters;
that shows up in my outputs like:
vpc_subnet_zone_letters: [
[0]: "a"
[1]: "b"
[2]: "c"
[3]: "d"
]
Finally, in another stack I want to load them and use them as part of a string input to another stack, and so far for the life of me I can’t get it to work:
var vpc_subnet_zone_letters = vpc.getOutput('vpc_subnet_zone_letters');
...
availabilityZones: [
`us-east-2${vpc_subnet_zone_letters.apply(x=>`${x[0]}`)}`,
`us-east-2${vpc_subnet_zone_letters.apply(x=>`${x[1]}`)}`,
],
straight-jordan-23612
08/22/2019, 12:43 AMstraight-jordan-23612
08/22/2019, 12:44 AMstraight-jordan-23612
08/22/2019, 12:46 AMpulumi:pulumi:Stack ff-data-import-lambda-dev running read pulumi:pulumi:StackReference factsfirstops/ff-infra/dev
pulumi:pulumi:Stack ff-data-import-lambda-dev running TypeError: Cannot read property 'outputs' of undefined
colossal-thailand-53880
08/22/2019, 2:00 AM500
server error. Please help us give you more money.high-translator-22614
08/22/2019, 2:05 AMdamp-room-71337
08/22/2019, 10:35 AMbitter-painter-81429
08/22/2019, 11:48 AMbest-xylophone-83824
08/22/2019, 11:56 AM~ gcp:container/cluster:Cluster: (update)
[id=gke01-london]
[urn=urn:pulumi:gke01-london::gcp-gke::gcp:container/cluster:Cluster::gke01-london]
[provider=urn:pulumi:gke01-london::gcp-gke::pulumi:providers:gcp::default_1_0_0_beta_1::1a4df25a-af6f-4fda-80df-2c8bd047655a]
~ minMasterVersion: "1.13.7-gke.19" => "1.13.7-gke.24"
~ nodeVersion : "1.13.7-gke.19" => "1.13.7-gke.24"
error: Plan apply failed: 1 error occurred:
* updating urn:pulumi:gke01-london::gcp-gke::gcp:container/cluster:Cluster::gke01-london: googleapi: Error 400: Must specify a field to update., badRequest
best-xylophone-83824
08/22/2019, 12:09 PMpulumi up --refresh
should discover that cloud resource was deleted, right? It was deleted due to 'deleteBeforeCreate' on a previous run, then creation failed, so now I am adding '--refresh' in a hope that pulumi will figure out that resource is not there anymore, but it still tries to update 😕