tall-librarian-49374
06/18/2019, 6:53 AMfaint-motherboard-95438
06/18/2019, 2:27 PMDeployment
configuration, I noticed it creates a new replicaset and does not delete the old one (or maybe it should update it, I don’t know). So it actually kills all the old pods in the old replicaset and creates the new one as expected, but now I have a stale useless replicasets.
Is this something I misconfigured somewhere or is this a bug ?
replicaset.apps/context-clusters-pvmtest-mqtt-5979fbcdbc 2 2 2 2m13s
replicaset.apps/context-clusters-pvmtest-mqtt-client-68fd4d4445 0 0 0 23m
replicaset.apps/context-clusters-pvmtest-mqtt-client-6b8bdfc4b7 2 2 2 2m13s
replicaset.apps/context-clusters-pvmtest-mqtt-f5bd9548f 0 0 0 25m
replicaset.apps/context-clusters-pvmtest-portal-567948dccd 2 2 2 2m13s
replicaset.apps/context-clusters-pvmtest-portal-6c5968cfcd 0 0 0 26m
bulky-businessperson-73745
06/18/2019, 3:53 PMelegant-crayon-4967
06/18/2019, 4:20 PMindex.ts
for aws & typescript?limited-rainbow-51650
06/18/2019, 4:20 PMterraform state import
(https://www.terraform.io/docs/import/index.html)proud-alarm-92546
06/18/2019, 5:09 PMnot found: verification code "code" not found
(which entirely amusing in it's repetition..elegant-crayon-4967
06/18/2019, 5:47 PMhandsome-actor-1155
06/18/2019, 6:15 PMUpdating (dev):
Type Name Status Info
pulumi:pulumi:Stack stream-demo-sensor-reading-aggregator-dev
> ├─ pulumi:pulumi:StackReference brianbrifri/stream-demo-services/dev read
> ├─ pulumi:pulumi:StackReference brianbrifri/stream-demo-infra/dev read
├─ docker:image:Image sensorReadingAggregator
~ └─ kubernetes:apps:ReplicaSet stream-demo-sensor-reading-aggregator updated [diff: ~spec]
Is my output but the replica set in k8s is unchanged. Is this expected behavior?proud-alarm-92546
06/18/2019, 8:04 PMpulumi/pulumi
first time running make
on a stock master, golangci-lint run
complains about a bunch of things that don't seem to be erroring in the travis builds. makes me wonder if there's golangci-link
version issue, or if there's a config somewhere that's not in the repo, or......
cmd/pulumi-language-nodejs/main.go:87:56: `langauge` is a misspelling of `language` (misspell)
cmdutil.InitTracing("pulumi-language-nodejs", "pulumi-langauge-nodejs", tracing)
(if I fix that one, it moves on to many others)
opened an issue - https://github.com/pulumi/pulumi/issues/2841full-dress-10026
06/18/2019, 9:36 PMbusy-air-16359
06/19/2019, 12:29 PMbusy-air-16359
06/19/2019, 12:29 PMbusy-air-16359
06/19/2019, 12:29 PMthankful-lamp-48382
06/19/2019, 1:59 PMthankful-lamp-48382
06/19/2019, 1:59 PMthankful-lamp-48382
06/19/2019, 2:22 PMthankful-lamp-48382
06/19/2019, 2:30 PMboundless-monkey-50243
06/19/2019, 3:18 PMterraform taint
, that I can tell Pulumi “that resource must be replaced”? (I don’t think I can manually remove it; it’s an AWS API Gateway deployment and those are archived rather than deleted.)full-dress-10026
06/19/2019, 4:17 PMloadBalancerInboundNatRulesIds: [pulumi.all(lbnatpool.map(v => v.id)).apply(id => id.map(v => v)[1])],
does not work. You cannot map
a NatPool
.broad-dog-22463
06/19/2019, 4:18 PMbored-river-53178
06/19/2019, 4:40 PMearly-musician-41645
06/19/2019, 5:53 PMpulumi up
and the error outputs:
error: Plan apply failed: Program run without the `pulumi` CLI; this may not be what you want (enable PULUMI_TEST_MODE to disable this error)
This started happening after I defined a new function as part of my custom resource
I'm using Pulumi v0.17.16
Any idea on a fix?full-dress-10026
06/19/2019, 6:01 PMazure.compute.ScaleSet
to provision VMs, can you have the scale set assign public IPs to the created VMs so you can ssh onto them?early-musician-41645
06/19/2019, 6:56 PM19 async function getServiceAccountAuth() {
20 const secret = await aws.secretsmanager.getSecretVersion({
21 secretId: "some-secret-name",
22 });
23 const secretString = secret.secretString
24 console.log("SECRETSTRING: "+secretString);
25
26 let username: string = JSON.parse(secretString)["username"];
27 let password: string = JSON.parse(secretString)["password"];
28
29 console.log("username: " + username);
30
31 return "Basic " + new Buffer(username + ":" + password).toString("base64");
32 }
When I run that function I get this:
error: Plan apply failed: Program run without the `pulumi` CLI; this may not be what you want (enable PULUMI_TEST_MODE to disable this error)
What am I doing wrong?full-dress-10026
06/19/2019, 7:01 PMosProfile
of a ScaleSet
I get this outputted from `pulumi up`:
azure:compute:ScaleSet azureDemo-ss2 updated [diff: ~osProfile]
However, the actual instances are not restarted. When changing customData
, I would expect instances to restart to apply the new customData.full-dress-10026
06/19/2019, 9:04 PMpulumi up
? Use case would be outputting a kubeconfig.full-dress-10026
06/19/2019, 11:11 PMlate-lawyer-23405
06/19/2019, 11:27 PMcolossal-room-15708
06/19/2019, 11:30 PMearly-musician-41645
06/19/2019, 11:55 PMasync delete
method of a dynamic resource provider?early-musician-41645
06/19/2019, 11:55 PMasync delete
method of a dynamic resource provider?async delete(id, props)
method requires some auth arguments to form a REST DELETE
request. For the async create(inputs)
I just added the auth data into the inputs
and had no trouble.
How can I make those available to delete
?white-balloon-205
06/20/2019, 12:01 AMearly-musician-41645
06/20/2019, 12:01 AMwhite-balloon-205
06/20/2019, 12:01 AMinputs
probably isn't right here - there won't be any inputs during a delete
.early-musician-41645
06/20/2019, 12:02 AMwhite-balloon-205
06/20/2019, 12:03 AMIt's more complicated - the auth is pulled from aws secretsmanagerThat should still be possible. Is it pulled from secrets manager at deployment time via
aws.secretsmanager.getSecretVersion
?early-musician-41645
06/20/2019, 12:04 AMaws-sdk
instead. So the secret is pulled like this:
28 var secretsmanager = new AWS.SecretsManager();
29 secretsmanager.getSecretValue({ SecretId: "eshamay-test" }, function(err: any, data: any) {
30 if (err) {
31 console.log("ERROR getting secret for service account", err);
32 throw err;
33 } else {
34 const savedSearch = new splunk.SavedSearch("foo-search", {
35 name: "foo-eshamay-test-1",
36 description: "eshamay's test search",
37 search: 'search index=online_prod source="*10ay*" earliest=-5m | stats count as Total',
38 splunkAuthSecret: data.SecretString,
39 });
40 }
41 });
42
pulumi.dynamic.Resource
81 export class SavedSearch extends pulumi.dynamic.Resource {
82 public readonly name: pulumi.Output<string>;
83
84 private static provider = new SavedSearchProvider();
85
86 constructor(name: string, props: SavedSearchInput, opts?: pulumi.CustomResourceOptions) {
87 super(SavedSearch.provider, name, props, opts);
88
89 SavedSearch.provider.setAuth(props.splunkAuthSecret);
90 }
91 }
The creds are still in the inputs
, but then I added a setter to the provider to create an instance variable that I can use in the delete
methodwhite-balloon-205
06/20/2019, 12:16 AMdelete
implementation is passed the old props
for the resource, so any credentials provided at creation time will be available on the props
.
Was that not working for you?
Note that the Pulumi program does not run at all during a destroy
- so there is no way to pass new values in during the deletes for a destroy - the only data you have available to you is either:
1. The old inputs from when the resource was created/updated.
2. The serialized implementation of the delete
body, which itself may have serialized in some state captured during that last update.