best-xylophone-83824
09/13/2019, 9:29 AMpanic: fatal: An assertion has failed: Kubernetes GVK is: "urn:pulumi:gke01-london::gcp-gke::gcp:compute/securityPolicy:SecurityPolicy::ingress-stable-protected-iap-whitelist-trusted-ips"
, full stack trace insidestocky-island-3676
09/13/2019, 10:42 AMreplace
instead of an update
for a resource?
We’re having some `gcp.container.Cluster`s (GKE clusters) and I want consider if a change introducing a replace of the whole cluster is worth it or not. If so, every service running it would need to be redeployed (not so nice).best-xylophone-83824
09/13/2019, 11:16 AMstocky-island-3676
09/13/2019, 11:23 AMpulumi refresh
shows differences where there are no one.
Here in the nodeConfig
on updating gcp:container/nodePool:NodePool
. Where relies this bug: Pulumi or Terraform provider? I.e., in which Github repo must I search for an issue?best-xylophone-83824
09/13/2019, 12:54 PMpulumi stack mv $oldURN $newURN
or even pulumi stack reparent $fromParentURN $toParentURN
abundant-umbrella-28158
09/13/2019, 12:55 PMquiet-wolf-18467
1.0
and 1.1
seems pretty broken due to change in the stack naming: https://github.com/pulumi/pulumi/issues/3223damp-room-71337
09/13/2019, 2:37 PMdynamic.Resource
properties - how do I return info from the backing cloud object via the Resource object here?
const TestProvider = {
async create(inputs) {
// some api call result
const derivedVal = "foobar";
return {
id: "id",
outs: { inputVal: inputs.inputVal, derivedVal: derivedVal
}
};
}
};
class TestResource extends pulumi.dynamic.Resource {
constructor(name, props, opts) {
super(TestProvider, name, props, opts);
}
}
const testResource = new TestResource("test-token", {
inputVal: "bar"
});
console.log(testResource.inputVal); // 'OutputImpl { ...'
console.log(testResource.derivedVal); // undefined
early-match-56268
09/13/2019, 3:25 PMearly-match-56268
09/13/2019, 3:26 PMrhythmic-finland-36256
09/13/2019, 3:56 PMServicePrincipal
authentication instead of the default CLI one. Now in one case the ServicePrincipal
I used had too few permissions to create `RoleAssignment`s. I now observe some inconsistencies between the pulumi state and what was created in the Azure subscription. Pulumi thinks everything but the `RoleAssignment`s has been created. With the corresponding permissions added to the ServicePrincipal
this now leads to the issue that the RoleAssignment
cannot be created as the desired ServicePrincipal
(not the login one) I want to assign the role doesn’t exist. This looks like a bug to me because Pulumi should not store resources (e.g. the ServicePrincipal
I wanted to create) if this was not successfully persisted at the provider level. Is there a way I can support debugging that case? I already did a pulumi refresh
which showed some resources as delete
but the case should be reproducible.full-dress-10026
09/13/2019, 6:19 PMpulumi up
with my k8s.apps.v1.Deployment
, k8s (or Pulumi?) replaced all existing pods immediately instead of replacing in a one-by-one fashion, waiting for the readinessProbe to become true. Is this something I need to configure Pulumi to do?quiet-wolf-18467
pulumi:providers:gcp (default_1_0_0):
error: no resource plugin 'gcp-v1.0.0' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource gcp v1.0.0`
##[error]Docker run failed with exit code 255
quiet-wolf-18467
plugin install
prior to the pulumi
command. pulumi
cli doesn't respect HOME=
, so it always installs plugins to getent
home, which isn't persisted by GitHub Actionsbitter-dentist-28132
09/13/2019, 9:47 PMreturn new Promise((resolve, reject) => {
let num = 0;
object1.apply(o => {
expect(o.prop1).toBe(something);
expect(o.prop2).toBe(somethingElse);
num++;
if (num === 2) {
done();
}
});
object2.apply(o => {
expect(o.prop1).toBe(something);
expect(o.prop2).toBe(somethingElse);
num++;
if (num === 2) {
done();
}
});
});
i know in QUnit you can do
const done = QUnit.done(2);
object1.apply(o => {
expect(o.prop1).toBe(something);
expect(o.prop2).toBe(somethingElse);
done();
});
object2.apply(o => {
expect(o.prop1).toBe(something);
expect(o.prop2).toBe(somethingElse);
done();
});
so i might just end up switching to that, but i'm wondering how you all run these kinds of tests with not-QUnitnice-cat-91582
09/15/2019, 1:31 AMnice-cat-91582
09/15/2019, 1:33 AMbest-waiter-16927
09/15/2019, 11:49 AMpulumi stack ls
command?incalculable-diamond-5088
09/15/2019, 8:34 PMpulumi:pulumi:Stack pubsub-service-pubsub-staging-shared debug: Setting AWS metadata API timeout to 100ms
panic: fatal: An assertion has failed
goroutine 187 [running]:
<http://github.com/pulumi/pulumi/pkg/util/contract.failfast(...)|github.com/pulumi/pulumi/pkg/util/contract.failfast(...)>
/private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/util/contract/failfast.go:23
<http://github.com/pulumi/pulumi/pkg/util/contract.Assert(...)|github.com/pulumi/pulumi/pkg/util/contract.Assert(...)>
/private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/util/contract/assert.go:26
<http://github.com/pulumi/pulumi/pkg/resource/deploy.NewDeleteStep(0xc0010d0f00|github.com/pulumi/pulumi/pkg/resource/deploy.NewDeleteStep(0xc0010d0f00>, 0xc001234d00, 0xc001128850, 0x68)
/private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/resource/deploy/step.go:238 +0x261
<http://github.com/pulumi/pulumi/pkg/resource/deploy.(*stepGenerator).GenerateDeletes(0xc0005e25a0|github.com/pulumi/pulumi/pkg/resource/deploy.(*stepGenerator).GenerateDeletes(0xc0005e25a0>, 0xc0014bfc00, 0x2, 0x0)
/private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/resource/deploy/step_generator.go:551 +0x77d
<http://github.com/pulumi/pulumi/pkg/resource/deploy.(*planExecutor).Execute.func3(0xc0015d98c0|github.com/pulumi/pulumi/pkg/resource/deploy.(*planExecutor).Execute.func3(0xc0015d98c0>, 0xc000239be0, 0xc0006e58f0, 0x24c7aa0, 0xc0010c3f40, 0x24c7aa0, 0xc0010c3f00, 0x10000, 0x1, 0xc000761400)
/private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/resource/deploy/plan_executor.go:155 +0x3d5
<http://github.com/pulumi/pulumi/pkg/resource/deploy.(*planExecutor).Execute(0xc000239be0|github.com/pulumi/pulumi/pkg/resource/deploy.(*planExecutor).Execute(0xc000239be0>, 0x24c7aa0, 0xc0010c3f00, 0x24c7ea0, 0xc000af8000, 0x7fffffff, 0x10000, 0x1, 0x0, 0x0)
/private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/resource/deploy/plan_executor.go:192 +0x511
<http://github.com/pulumi/pulumi/pkg/resource/deploy.(*Plan).Execute(...)|github.com/pulumi/pulumi/pkg/resource/deploy.(*Plan).Execute(...)>
/private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/resource/deploy/plan.go:330
<http://github.com/pulumi/pulumi/pkg/engine.(*planResult).Walk.func1(0x24c7ea0|github.com/pulumi/pulumi/pkg/engine.(*planResult).Walk.func1(0x24c7ea0>, 0xc000af8000, 0xc001568160, 0x24c7aa0, 0xc0010c3f00, 0x20e5401, 0xc0006e58e0, 0xc0015d96e0)
/private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/engine/plan.go:182 +0x13b
created by <http://github.com/pulumi/pulumi/pkg/engine.(*planResult).Walk|github.com/pulumi/pulumi/pkg/engine.(*planResult).Walk>
/private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/engine/plan.go:173 +0x11b
Is that a known issue?fierce-cpu-94517
09/16/2019, 1:14 PMpulumi up
always detects a change in an EBS volume attachment though nothing changed:
$ pulumi up
Previewing update (acmecorp-demo):
Type Name Plan Info
pulumi:pulumi:Stack private-cloud-acmecorp-demo
+- ├─ aws:ec2:Instance services replace [diff: ~ebsBlockDevices]
...
Resources:
+-8 to replace
156 unchanged
Do you want to perform this update? details
pulumi:pulumi:Stack: (same)
[urn=urn:pulumi:acmecorp-demo::private-cloud::pulumi:pulumi:Stack::private-cloud-acmecorp-demo]
++aws:ec2/instance:Instance: (create-replacement)
[id=i-0eba90d7bd7c11af4]
[urn=urn:pulumi:acmecorp-demo::private-cloud::aws:ec2/instance:Instance::services]
[provider=urn:pulumi:acmecorp-demo::private-cloud::pulumi:providers:aws::default_0_18_27::4e650a8e-8d3d-4c3c-a9d1-b31c8638bd95]
~ ebsBlockDevices: [
~ [0]: {
~ deleteOnTermination: true => true
~ deviceName : "/dev/sdf" => "/dev/sdf"
+ encrypted : true
+ volumeSize : 100
+ volumeType : "gp2"
}
]
+-aws:ec2/instance:Instance: (replace)
[id=i-0eba90d7bd7c11af4]
[urn=urn:pulumi:acmecorp-demo::private-cloud::aws:ec2/instance:Instance::services]
[provider=urn:pulumi:acmecorp-demo::private-cloud::pulumi:providers:aws::default_0_18_27::4e650a8e-8d3d-4c3c-a9d1-b31c8638bd95]
~ ebsBlockDevices: [
~ [0]: {
~ deleteOnTermination: true => true
~ deviceName : "/dev/sdf" => "/dev/sdf"
+ encrypted : true
+ volumeSize : 100
+ volumeType : "gp2"
}
]
clean-van-8624
09/16/2019, 2:43 PMlittle-garage-43399
09/16/2019, 3:55 PMsalmon-beard-79336
09/16/2019, 4:03 PMManaged Identities
for Azure API Management services?
Required in order to enable custom hostnameConfiguration
const service = new azure.apimanagement.Service(`${prefix}-service`, {
resourceGroupName: resourceGroup.name,
sku: {
name: 'Developer',
capacity: 1
},
publisherName: 'Bob',
publisherEmail: 'alex.b@d.c',
hostnameConfiguration: {
proxies: [{
hostName: domainName,
// certificate: '',
// certificatePassword: '',
keyVaultId: pulumi.interpolate`${keyVault.vaultUri}certificates/generated-cert/90951e125ada483c8a1e76440fa484c7`,
negotiateClientCertificate: false,
defaultSslBinding: true
}]
}
})
incalculable-engineer-92975
09/16/2019, 5:28 PMincalculable-engineer-92975
09/16/2019, 5:28 PMincalculable-engineer-92975
09/16/2019, 5:28 PMincalculable-engineer-92975
09/16/2019, 5:29 PMincalculable-engineer-92975
09/16/2019, 5:29 PMripe-dinner-40604
09/16/2019, 6:44 PMgray-nest-70702
09/16/2019, 8:18 PM