gentle-diamond-70147
05/24/2019, 1:06 PMbitter-island-28909
05/24/2019, 1:59 PMpulumi refresh
, Pulumi now wants to spuriously update or replace a bunch of resources that I can assert haven’t actually changed.
Some examples of diffs that look wrong to me (on various resources):
~ records: [
~ [0]: "10.3.0.222" => output<string>
]
~ memory : "512" => 512
- volumes : []
~ applications : [
~ [0]: "Spark" => "Hadoop"
~ [2]: "Hadoop" => "Presto"
~ [3]: "Presto" => "Spark"
]
This occurs immediately after a sequence of pulumi up
, pulumi refresh
, pulumi up
, without any alteration of my scripts or deliberate modification of deployed resources.orange-policeman-59119
05/24/2019, 5:41 PMDiagnostics:
kubernetes:extensions:Deployment ([redacted]):
warning: Refreshed resource is in an unhealthy state:
* Resource '[redacted]' was created but failed to initialize
* Minimum number of Pods to consider the application live was not attained
Here's what the resources look like:
$ kubectl -n ... get deployment
NAME READY UP-TO-DATE AVAILABLE AGE
[deployment] 3/3 3 3 11h
$ kubectl -n ... get rs
NAME DESIRED CURRENT READY AGE
[old] 0 0 0 11h
[new] 3 3 3 6m4s
busy-umbrella-36067
05/24/2019, 5:42 PMvalues
using kubernetes.helm.v2.Chart
?targetPorts
on an Ingress Chart// create ingress controller
const ingressController = new k8s.helm.v2.Chart(
name,
{
fetchOpts: {
repo: "<https://helm.nginx.com/stable>"
},
chart: "nginx-ingress",
version: "0.3.0",
values: {
controller: {
service: {
targetPorts: {
https: "http",
http: "http"
},
annotations: {
"<http://service.beta.kubernetes.io/aws-load-balancer-ssl-cert|service.beta.kubernetes.io/aws-load-balancer-ssl-cert>": certificate.arn,
"<http://service.beta.kubernetes.io/aws-load-balancer-backend-protocol|service.beta.kubernetes.io/aws-load-balancer-backend-protocol>": "http",
"<http://service.beta.kubernetes.io/aws-load-balancer-ssl-ports|service.beta.kubernetes.io/aws-load-balancer-ssl-ports>": "https",
"<http://service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout|service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout>": "3600"
}
}
}
}
}, {});
}
orange-policeman-59119
05/24/2019, 6:34 PMInput<>
values? I'm seeing this since updating @pulumi/kubernetes
to 0.23:
Error: render error in "[redacted]/secret.yaml": template: [redacted]/secret.yaml:15:49: executing "[redacted]/secret.yaml" at <b64enc>: wrong type for value; expected string; got map[string]interface {}
Only change was updating the Pulumi kubernetes provider.orange-policeman-59119
05/24/2019, 6:35 PMvalues: { foo: { bar: { secretValue: $someInput<string> }}}
average-dream-51210
05/25/2019, 11:50 PMlittle-dinner-9110
05/26/2019, 2:18 AMlittle-dinner-9110
05/26/2019, 2:20 AMproud-artist-4864
05/27/2019, 7:35 AMsquare-plumber-80712
05/27/2019, 8:41 AMjolly-egg-4894
05/27/2019, 9:58 AMcolossal-room-15708
05/27/2019, 11:20 AMfaint-motherboard-95438
05/28/2019, 11:12 AMindex.ts(109,5): error TS2322: Type '{ gcp: Provider; kubernetes: Provider; }' is not assignable to type 'Record<string, ProviderResource>'.
index.ts(134,5): error TS2322: Type '{ gcp: Provider; kubernetes: Provider; }' is not assignable to type 'Record<string, ProviderResource>'.
index.ts(170,5): error TS2322: Type '{ gcp: Provider; kubernetes: Provider; }' is not assignable to type 'Record<string, ProviderResource>'.
index.ts(188,5): error TS2322: Type '{ gcp: Provider; kubernetes: Provider; }' is not assignable to type 'Record<string, ProviderResource>'.
I’m creating providers for gcp and kubernetes with new gcp.Provider()
and new k8s.Provider()
from @pulumi/gcp
and @pulumi/kubernetes
respectively and I’m passing them down in all my components opts
argument.
Everything was perfectly working before…gray-hair-49169
05/28/2019, 12:13 PMconst testPostgresServer = new azure.postgresql.Server("testserver", {
administratorLogin: "USER",
administratorLoginPassword: "PASS",
location: config.location,
name: `${config.prefix}-postgresql-01`,
resourceGroupName: config.resourceGroup.name,
sku: {
capacity: 1,
family: "Gen5",
name: "B_Gen5_1",
tier: "Basic",
},
sslEnforcement: "Enabled",
storageProfile: {
backupRetentionDays: 7,
geoRedundantBackup: "Disabled",
storageMb: 5120,
},
version: "9.5",
});
const testConfiguration = new azure.postgresql.Configuration("testconf", {
name: "backslash_quote",
resourceGroupName: config.resourceGroup.name,
serverName: testPostgresServer.name,
value: "on",
});
const testDatabase = new azure.postgresql.Database("testdb", {
charset: "UTF8",
collation: "English_United States.1252",
name: "exampledb",
resourceGroupName: config.resourceGroup.name,
serverName: testPostgresServer.name,
});
Thanks 🙂stocky-spoon-28903
05/28/2019, 12:18 PMstocky-spoon-28903
05/28/2019, 12:21 PMbetter-rainbow-14549
05/28/2019, 5:21 PMbetter-rainbow-14549
05/28/2019, 5:21 PMstocky-spoon-28903
05/28/2019, 5:23 PMbetter-rainbow-14549
05/28/2019, 5:23 PMbetter-rainbow-14549
05/28/2019, 5:23 PMstocky-spoon-28903
05/28/2019, 5:24 PMnode_modules
directly to get a preview?stocky-spoon-28903
05/28/2019, 5:24 PMyarn link
?stocky-spoon-28903
05/28/2019, 5:24 PMnpm link
etc)better-rainbow-14549
05/28/2019, 5:24 PMbetter-rainbow-14549
05/28/2019, 5:24 PMtsc
it fine and it will use the link, but when pulumi rebuilds the typescript it ignores the linksbetter-rainbow-14549
05/28/2019, 5:24 PMbetter-rainbow-14549
05/28/2019, 5:25 PMstocky-spoon-28903
05/28/2019, 5:25 PMyarn link
pretty heavily in our development (or at least, I do!)