wet-noon-14291
06/11/2020, 10:48 AMCan I have one project that does the build image and also deploys based on an input flag when running, or should I have one project for package the app and one for deploy?pulumi up
average-receptionist-65239
06/11/2020, 11:20 AM-import * as kx from "@pulumi/kubernetesx";
It's a change to my index.ts
. Has anyone else experienced this kind of thing?
Something similar happened a couple of days ago when I reordered my imports but I didn't stop to investigate.white-airport-48392
06/11/2020, 2:58 PMconst service = new awsx.ecs.EC2Service(name, {
name: `${name}-${utils.resolveStack()}`,
cluster: cluster,
subnets: ["xxxxx"],
taskDefinitionArgs: {
networkMode: "bridge",
taskRole: ecsConfig["taskRole"],
logGroup: null,
executionRole: ecsConfig["executionRole"],
containers: {
test: {
image: "xxxxx",
cpu: 1024,
memory: 1024,
portMappings: [listener]
}
}
},
desiredCount: 0
});
The above config creates the Service with a loadbalancer/target group that is configured over port 8080 , this forces a new target to be registered to the target group over 8080 only ,
But in my case I want the targets to register over ephemeral ports
If I want multiple docker containers to run on the same container instance , I need dynamic mapping which is configured via
portMappings:[
{
hostPort:0,
containerPort:8080
}]
If I do the above , the Service is created without a load balancer ,
Is there a way to get this to work per
https://aws.amazon.com/premiumsupport/knowledge-center/dynamic-port-mapping-ecs/
Any help is appreciated πbitter-zebra-93800
06/11/2020, 7:33 PMsparse-state-34229
06/11/2020, 7:41 PMgentle-diamond-70147
06/11/2020, 7:50 PMthankful-laptop-55220
06/11/2020, 10:12 PM__pulumiOutput
and similar as values for g
. preview:
pulumi:pulumi:Stack gcso-k8-dev
+ ββ aws:ec2:LaunchTemplate __pulumiOutput create
+ ββ aws:ec2:LaunchTemplate promise create
+ ββ aws:ec2:LaunchTemplate toString create
+ ββ aws:ec2:LaunchTemplate toJSON create
+ ββ aws:ec2:LaunchTemplate allResources create
+ ββ aws:ec2:LaunchTemplate resources create
+ ββ aws:ec2:LaunchTemplate isSecret create
+ ββ aws:ec2:LaunchTemplate isKnown create
what am i not grasping?thankful-laptop-55220
06/11/2020, 10:17 PMup
operation? granted that leaves preview rather useless at predicting what resources would be CRUD'ed, but is it possible?millions-judge-24978
06/11/2020, 10:25 PMgifted-city-99717
06/11/2020, 11:05 PMproject_root
βββ Pulumi.yaml
βββ README.md
βββ elasticsearch/
βββ fargate/
βββ go.mod
βββ go.sum
βββ influxdb/
βββ main.go
βββ main_test.go
βββ s3sink/
βββ Pulumi.sink-dev.yaml
βββ Pulumi.sink-stage.yaml
βββ Pulumi.sink-prod.yaml
βββ handler/
βββ handler.zip
βββ policies.go
βββ sink_bucket.go
βββ sink_bucket_test.go
When I try running pulumi up
I get an error saying config hasnβt been set. I was wondering if anyone has any pointers (aside from moving the stack yaml files to the same level as the project)β¦little-dentist-8150
06/12/2020, 1:59 AMbusy-honey-73811
06/12/2020, 12:28 PMmillions-furniture-75402
06/12/2020, 12:57 PMacoustic-rose-89683
06/12/2020, 2:07 PMcrooked-window-31802
06/12/2020, 2:13 PMbusy-soccer-65968
06/12/2020, 5:29 PMenough-kite-69616
06/12/2020, 6:04 PMenough-kite-69616
06/12/2020, 6:05 PMimportant-appointment-55126
06/12/2020, 9:55 PMrich-napkin-40911
06/13/2020, 12:03 AMelegant-dress-88912
06/13/2020, 2:21 AM$ pulumi up
...
Diagnostics:
pulumi:providers:gcp (default_2_1_1):
error: no resource plugin 'gcp-v2.1.1' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource gcp v2.1.1`
Version number comes from plugin random
- I can prove this by upgrading it:
$ yarn add @pulumi/random@2.1.2
$ pulumi up
...
Diagnostics:
pulumi:providers:gcp (default_2_1_2):
error: no resource plugin 'gcp-v2.1.2' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource gcp v2.1.2`
elegant-dress-88912
06/13/2020, 2:22 AMelegant-dress-88912
06/13/2020, 2:23 AMelegant-dress-88912
06/13/2020, 2:26 AMelegant-dress-88912
06/13/2020, 2:32 AMelegant-dress-88912
06/13/2020, 2:34 AMelegant-dress-88912
06/13/2020, 2:56 AMpulumi stack export > stack.json
2. manually add CRD into stack.json
3. import state back with pulumi stack import --file stack.json
4. refresh resource state with pulumi refresh -t 'urn:...'
- this is to prevent replacement of CRD
5. sync with regular pulumi up
but this is rather tedious and I think it'll be useful to have some pulumi subcommand for this.bitter-australia-87528
06/13/2020, 4:32 AMorange-fountain-17148
06/13/2020, 10:23 AMbored-finland-61499
06/13/2020, 3:54 PM