important-leather-28796
02/19/2019, 3:29 PMindex.ts
has certain things clusterName, kubeconfig
exported, but there is no explanation why. I’m assuming pulumi needs these named exports, but feeling a bit in the dark. I’m expecting the ts to be strongly typed; I was expecting to export something conforming to an interface
for example.colossal-beach-47527
02/19/2019, 4:30 PMbusy-umbrella-36067
02/19/2019, 6:42 PM.apply
method causes all of the annotations to be planned for removal.
I would expect Pulumi to wait until the security group is created to modify the Ingress (display the new annotation value as computed), is there a better way to go about this?
let Ingress = new k8s.extensions.v1beta1.Ingress("xxxxxxx-xxx", {
metadata: {
annotations: {
'<http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>': 'alb',
'<http://alb.ingress.kubernetes.io/certificate-arn|alb.ingress.kubernetes.io/certificate-arn>': awsCertificate.arn,
'<http://alb.ingress.kubernetes.io/listen-ports|alb.ingress.kubernetes.io/listen-ports>': '[{"HTTPS": 443}]',
'<http://alb.ingress.kubernetes.io/scheme|alb.ingress.kubernetes.io/scheme>': 'internet-facing',
'<http://alb.ingress.kubernetes.io/target-type|alb.ingress.kubernetes.io/target-type>': 'ip',
'<http://alb.ingress.kubernetes.io/security-groups|alb.ingress.kubernetes.io/security-groups>': securityGroup.id.apply(id => {return id})
}
},
~ kubernetes:extensions/v1beta1:Ingress: (update)
[id=default/xxxx-xx-xxx]
[urn=urn:pulumi:xxxxxx-staging::xxxxxxxxx::kubernetes:extensions/v1beta1:Ingress::xxxxxx-xxxxxxx]
~ metadata : {
~ annotations: {
- <http://alb.ingress.kubernetes.io/certificate-arn|alb.ingress.kubernetes.io/certificate-arn> : "arn:aws:acm:xx-west-1:xxxxxxxxxxxx:certificate/xxxxxxxxxxxxx"
- <http://alb.ingress.kubernetes.io/inbound-cidrs|alb.ingress.kubernetes.io/inbound-cidrs> : "xxxxxxxxxxxxxx"
- <http://alb.ingress.kubernetes.io/listen-ports|alb.ingress.kubernetes.io/listen-ports> : "[{\"HTTPS\": 443}]"
- <http://alb.ingress.kubernetes.io/scheme|alb.ingress.kubernetes.io/scheme> : "internet-facing"
- <http://alb.ingress.kubernetes.io/target-type|alb.ingress.kubernetes.io/target-type> : "ip"
- <http://kubernetes.io/ingress.class|kubernetes.io/ingress.class> : "alb"
}
}
important-leather-28796
02/19/2019, 6:53 PMblue
is currently running):
1. stand up a new set of integration tested images as green
2. smoke test
3. apply update to the traefik service to route to the green
stack
4. tear down the blue
stack
Am I overthinking this? In all likelihood the heterogeneous set of services will be fine but I am just trying to identify all potential points of failure for CD. Any thoughts welcome with regards to strategy and pulumi usagebrave-salesmen-42327
02/19/2019, 8:41 PMset PULUMI_CONFIG_PASSPHRASE to remember
but when I do that, it does't seem to work.
[git::secrets]$ echo ${PULUMI_CONFIG_PASSPHRASE}
secret
[git::secrets]$ p config --show-secrets
Enter your passphrase to unlock config/secrets
(set PULUMI_CONFIG_PASSPHRASE to remember):
error: incorrect passphrase
[git::secrets]$
Ed. Note: I just pressed enter here, resulting in the 'incorrect passphrase' message.
To show that it is the correct password stored in my config passphrase shell var:
[git::secrets]$ p config --show-secrets
Enter your passphrase to unlock config/secrets
(set PULUMI_CONFIG_PASSPHRASE to remember):
KEY VALUE
aws:region us-east-1
info useless
secrets SuperSecret
blue-answer-29496
02/19/2019, 9:01 PMblue-answer-29496
02/19/2019, 9:01 PMfaint-vegetable-61837
02/19/2019, 9:04 PMpulumi update
on a stack to create RDS instances. Got failed to complete update: [404] Not Found: Update '1ac5fad4-38d6-465e-9b21-742c277e252a' not found
error on one of the instances. It was actually created in AWS. Followed the steps in the troubleshooting guide (cancel update, export / import, refresh). This does not pick up the created instance. When I try to run pulumi update
again, it fails because the instance already exists. Would be great if there were a better way to handle it - instead of cancelling update, resolving it manually by pointing at the created resource ARN, for exampleimportant-leather-28796
02/19/2019, 9:15 PMindex.ts
, should this work:
import { Config } from '@pulumi/pulumi'
const config = new Config()
export const dbUser = config.require('dbUser')
with pulumi stack output dbUser
?
Currently I get error: current stack does not have output property 'dbUser'
important-leather-28796
02/19/2019, 10:40 PMlet additionalZones: string[] = []
if (config.get('clusterAdditionalZones')) {
additionalZones = config.get('clusterAdditionalZones')!.split(',')
}
export const clusterAdditionalZones = additionalZones
with config yml:
config:
deployment:clusterAdditionalZones: us-central1-a,us-central1-b
I tried a string[] in the yaml and it rejected it with line 7: cannot unmarshal !!seq into string
helpful-ice-5738
02/19/2019, 10:43 PMA map of request query string parameters and headers that should be passed to the integration. For example:
import * as pulumi from "@pulumi/pulumi";
would define that the header X-Some-Header and the query string some-query-param must be provided on the request, or
brainy-magician-83981
02/20/2019, 1:27 AMincalculable-angle-91273
02/20/2019, 2:15 AMistio-autogenerated-k8s-ingress
Gateway object that I don’t want to deploy. Can I use a transformation to achieve this? I tried using a delete obj
and obj = {}
but it still deploys the gateway.important-leather-28796
02/20/2019, 2:04 PMnew gcp.container.Cluster
, having a few problems mapping the last few cli options. I tried nodePools
but it doesn’t seem like the right thing based on the docs and it doesn’t typecheck. Where can I find these mappings or are they unsupported?
doc: https://pulumi.io/reference/pkg/nodejs/@pulumi/gcp/container/#Cluster
gcloud beta container clusters create \
--enable-autorepair \
--enable-autoscaling \
--enable-autoupgrade \
--enable-cloud-logging \
--enable-cloud-monitoring \
important-leather-28796
02/20/2019, 3:14 PMpulumi-kubernetes
package.json is preventing a green build for us. I have PR’d a fix. A hotfix release would be appreciated. https://github.com/pulumi/pulumi-kubernetes/pull/441busy-daybreak-68237
02/20/2019, 4:34 PMbusy-daybreak-68237
02/20/2019, 4:34 PMbusy-daybreak-68237
02/20/2019, 4:34 PMbusy-daybreak-68237
02/20/2019, 4:35 PMchilly-dusk-63796
02/20/2019, 6:03 PM6:30pm
- join us for free food, drinks, swag, and most importantly - great talks! https://www.meetup.com/Pulumi-Seattle/events/258138687/lemon-greece-30910
02/20/2019, 7:22 PMhelpful-ice-5738
02/20/2019, 7:27 PMconst _301_method = new aws.apigateway.MethodResponse("301Method", {
httpMethod: demo_method_get.httpMethod,
resourceId: demo_resource_with_params.id,
restApi: demo_api.id,
statusCode: "301",
responseParameters: {"method.response.header.Location": true}
});
const _301_integration = new aws.apigateway.IntegrationResponse("301Integration", {
httpMethod: demo_method_get.httpMethod,
resourceId: demo_resource_with_params.id,
restApi: demo_api.id,
statusCode: _301_method.statusCode,
responseParameters: {"method.response.header.Location": true}
}, {dependsOn: [demo_integration_get, _301_method]});
and get the response from AWS: Plan apply failed: Error creating API Gateway Integration Response: BadRequestException: Invalid mapping expression specified: Validation Result: warnings : [], errors : [Invalid mapping expression specified: 1]
full-dress-10026
02/20/2019, 7:49 PMpulumi up
with my `FargateService`:
updating urn:pulumi:app-dev::app::awsx:x:ecs:FargateService$aws:ecs/service:Service::http-backend: timeout while waiting for state to become 'true' (last state: 'false', timeout: 10m0s)
Not sure what causes that because the service is correctly deployed and currently healthy. Any ideas?gifted-island-55702
02/20/2019, 7:54 PMpulumi up
Previewing update (dev):
Type Name Plan
pulumi:pulumi:Stack example-dev
where example
is my project name and dev
is my stack namegifted-island-55702
02/20/2019, 7:55 PM<project>-<stack>
formatgifted-island-55702
02/20/2019, 8:00 PMurn:pulumi:dev::example::pulumi:pulumi:Stack::example-dev
.
Is this intended?orange-tailor-85423
02/20/2019, 8:45 PMorange-tailor-85423
02/20/2019, 8:47 PMproud-tiger-5743
02/20/2019, 8:49 PMconst input = new aws.s3.Bucket('inputbucket')
input.onObjectCreated('testing',(event,context)=> {
console.log(event)
},{keyPrefix: ".csv"},)
Is there a way to alter the IAM execution role?