red-football-97286
07/15/2019, 9:43 AMred-football-97286
07/15/2019, 9:44 AMbillions-lock-80282
07/15/2019, 2:31 PMbillions-lock-80282
07/15/2019, 2:32 PMexport const nginx = new k8s.helm.v2.Chart("nginx-ingress", {
repo: "stable",
version: "0.24.1",
chart: "nginx-ingress",
transformations: [addNamespace],
namespace: "nginx",
values: {
rbac: {create: true},
controller: {
publishService: {enabled: true},
stats: {enabled: true},
service: {
type: "LoadBalancer",
externalTrafficPolicy: "Local",
loadBalancerIP: lbIp
},
image: {tag: "0.24.1"}
}
}
}, { dependsOn: [nsnginx], provider: clusterProvider });
billions-lock-80282
07/15/2019, 2:32 PMconst certmanagerResources = new ConfigFile("cmResources", {
file: "<https://github.com/jetstack/cert-manager/releases/download/v0.8.1/cert-manager.yaml>",
},{ dependsOn: [nginx, primaryPool], provider: clusterProvider });
billions-lock-80282
07/15/2019, 2:33 PMbitter-island-28909
07/15/2019, 3:08 PMrandom
module. However, using the following code, the result
value of the RandomString
resource is still present in plaintext in the state (even though it’s correctly hidden as an attribute of the SSM Parameter.)
let password = pulumi.secret(new random.RandomString("my-password", {
length: 32
}).result);
let param = new aws.ssm.Parameter("my-password", {
name: "/my/password",
type: "SecureString",
value: password
});
worried-engineer-33884
07/15/2019, 5:43 PMworried-engineer-33884
07/15/2019, 5:43 PMpulumi login --local
and now I want to login to the cloud service, but pulumi login
keeps re-logging in to my local machinebillowy-garage-68819
07/15/2019, 6:14 PMboundless-monkey-50243
07/15/2019, 6:46 PM--acl bucket-owner-full-control
? Using Pulumi in a multi-account setup is otherwise kind of prohibitive.worried-engineer-33884
07/15/2019, 7:17 PMcuddly-eye-68174
07/15/2019, 7:23 PMswift-painter-31084
07/16/2019, 12:56 AMhttp-header
condition, but it looks like Terraform only supports path-pattern
and http_host
.
https://www.terraform.io/docs/providers/aws/r/lb_listener_rule.html#values
It looks like there are many more rules in the console for this:swift-painter-31084
07/16/2019, 12:57 AMbroad-dog-22463
07/16/2019, 1:00 AMbroad-dog-22463
07/16/2019, 1:00 AMbroad-dog-22463
07/16/2019, 1:00 AM// The field in the HTTP request. The following are the possible values:
//
// * http-header
//
// * http-request-method
//
// * host-header
//
// * path-pattern
//
// * query-string
//
// * source-ip
broad-dog-22463
07/16/2019, 1:00 AMbroad-dog-22463
07/16/2019, 1:01 AMswift-painter-31084
07/16/2019, 1:01 AM{
field: 'http-header',
httpHeaderName: 'Origin',
values: [ '*<http://snopes.com|snopes.com>*', '*snopes.local*' ],
},
broad-dog-22463
07/16/2019, 1:01 AMbroad-dog-22463
07/16/2019, 1:02 AMswift-painter-31084
07/16/2019, 1:04 AMjolly-egg-4894
07/16/2019, 12:37 PM.onObjectCreated()
lambda (in typescript) to nodejs10.x
or am I looking at completely recreating the BucketEventSubscription
class?
I’ve looked at the options that are passed through to the handler but it’s just { parent: this }
rapid-eye-32575
07/16/2019, 12:39 PMCustomResource
-objects are broken for me with the current release (I'm using v0.17.22
). I always get the following error:
TypeError: opts.parent.__aliases is not iterable
at new Resource ([...]/node_modules/@pulumi/pulumi/resource.js:117:51)
at new CustomResource ([...]/node_modules/@pulumi/pulumi/resource.js:270:9)
at new Resource ([...]/node_modules/@pulumi/pulumi/dynamic/index.js:40:9)
at new DatabaseUser ([...]/src/database/database-user.ts:7:9)
at [...]/src/database/gcp/gcp-database-cluster.ts:64:13
The instance of GCPDatabaseCluster
(which has no aliases) is the parent of a DatabaseUser
(again without aliases). Maybe this has something to do with the new feature of renaming resources (https://github.com/pulumi/pulumi/pull/2774)? Has anyone seen a similar behavior? The code still worked last week ago 🤔flaky-engine-87606
07/16/2019, 2:18 PMgcp:storage:BucketACL (bucket-acl):
error: Plan apply failed: all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:52527: connect: connection refused"
boundless-monkey-50243
07/16/2019, 5:42 PM--debug
is not particularly helpful. Is there a way to get more information, like "what resource is wrong"?handsome-actor-1155
07/16/2019, 6:41 PMconst ecr = new aws.ecr.Repository("ecr", {
name: "stream-app/corrective-action-producer"
});
const ecrCreds = ecr.registryId.apply(async (registryId) => {
const credentials = await aws.ecr.getCredentials({
registryId: registryId,
});
const decodedCredentials = Buffer.from(credentials.authorizationToken, "base64").toString();
const [username, password] = decodedCredentials.split(":");
return { server: credentials.proxyEndpoint, username, password };
});
return new docker.Image("correctiveActionProducer", {
imageName: ecr.repositoryUrl,
build: "./",
registry: ecrCreds
});
broad-dog-22463
07/16/2019, 9:57 PM