brash-plastic-65797
09/27/2019, 6:35 PMadamant-dress-73325
09/27/2019, 7:34 PMconst vpc = awsx.ec2.Vpc.fromExistingIds("vpc", {
privateSubnetIds: vpcPrivateSubnetIds,
publicSubnetIds: vpcPublicSubnetIds,
vpcId
});
cool-egg-852
09/27/2019, 8:41 PMflat-guitar-86436
09/27/2019, 8:48 PMpulumi: warning: A new version of Pulumi is available. To upgrade from version '1.1.0' to '1.2.0', run
$ brew upgrade pulumi
or visit <https://pulumi.com/docs/reference/install/> for manual instructions and release notes.
I’m running pulumi in ci, is there a way to remove the warning?elegant-dress-88912
09/28/2019, 10:20 AM-target
option for terraform)?elegant-dress-88912
09/28/2019, 10:31 AMpulumi up [template|url] [flags]
- what actually this [template|url]
part means?bitter-spoon-36677
09/28/2019, 1:10 PMpulumi up
I'm getting this error:
error: could not get cloud url: unmarshalling credentials file: unexpected end of JSON input
I am using version 1.1.0 on a Mac
EDIT: fixed it by deleting the ~/.pulumi foldercold-car-23440
09/28/2019, 10:27 PMcold-car-23440
09/28/2019, 10:27 PMDo you want to perform this destroy? yes
Destroying (dev):
Type Name Status Info
pulumi:pulumi:Stack pulumi-vault-dev
- ├─ azure:network:VirtualNetwork puluminet **deleting failed** error: Plan apply failed: deleting urn:pulumi:dev::pulumi-vault::azure:network/virtualNetwork:VirtualNetwork::
- ├─ azure:msi:UserAssignedIdentity consulmsi deleted
- ├─ azure:network:NetworkInterface vault-nic-0 deleting...
- ├─ azure:network:NetworkInterface consul-nic-1 deleting...
- ├─ azure:network:NetworkInterface vault-nic-2 deleting...
- ├─ azure:core:ResourceGroup vault-cluster-rg deleting...
- ├─ azure:network:NetworkInterface vault-nic-1 deleting...
- ├─ azure:msi:UserAssignedIdentity vaultmsi deleted
- ├─ azure:network:Subnet hcsubnet deleting...
- ├─ azure:network:NetworkInterface consul-nic-2 deleting...
- ├─ azure:network:NetworkInterface consul-nic-3 deleting...
- ├─ azure:network:NetworkInterface consul-nic-4 deleting...
- └─ azure:network:NetworkInterface consul-nic-0 deleting...
miniature-chef-87843
09/29/2019, 4:48 AM@pulumi/cloud
seems to have the the nice HttpServer
abstraction, but it's not clear what the status of that package is. It sounds like @pulumi/awsx?
would be the next best consideration here, but it's not clear how I'd put all these pieces together simplyminiature-chef-87843
09/29/2019, 4:54 AMworried-city-86458
09/29/2019, 7:29 PMnice-cat-91582
09/29/2019, 7:30 PMearly-intern-90238
09/30/2019, 12:10 AMearly-intern-90238
09/30/2019, 12:21 AMbroad-pencil-85643
09/30/2019, 6:02 AMdev/applications/api-content
, staging/applications/api-content
, and prod/applications/api-content
. Each of these directories have their own Terraform configs that might describe an S3 bucket or two, the EB app, an EB environment (or two), DBs, etc. Importantly, they're not all the same underlying infrastructure/resources.
Initially I figured re-creating this setup could be done by having, e.g., an api-content
project with dev
, staging
, and prod
stacks. But since, for example, there might not be an S3 bucket in the dev
stack whereas there is in staging
and prod
, it started to look like there would be a lot of if/else statements in my Pulumi source files. Do you think it might make more sense to create a project per environment, each with a single stack? That way I could ensure the Pulumi source is tailored specifically to each environment, and can still have something like a common project/stack that each environment pulls from for conventions/components shared between these environments.billions-lock-80282
09/30/2019, 1:50 PMstocky-nail-30268
09/30/2019, 3:55 PM<https://www.pulumi.com/blog/testing-your-infrastructure-as-code-with-pulumi/#deployment-testing>
, hit an issue straight away.
I've just copied the code verbatim from that post, and it seems I'm hitting an issue with ../github.com/pulumi/pulumi/pkg/resource/deploy/providers/registry.go:326:30: multiple-value uuid.NewV4() in single-value context
. Seems to be an issue with satori/go.uuid
returning err
for NewV4()
as well, but I feel like others would have come across this issue too, so, have I got something obviously wrong?stocky-xylophone-20575
09/30/2019, 4:27 PMgoogle-beta
) in calling for creating cloud run
my_endpoint = cloudrun.Service("my_api_endpoint",
spec={
"containers": [
{"image":"<http://gcr.io/endpoints-release/endpoints-runtime-serverless:1|gcr.io/endpoints-release/endpoints-runtime-serverless:1>"}
]
},
location="us-east1", metadata={"namespace": "myproject"},)
, i keep getting 400 error for this , still dont the reason but speculating this could be a starting pointacceptable-army-69872
09/30/2019, 4:40 PMbrave-angle-33257
09/30/2019, 6:49 PMgoogle-protobuf
acoustic-noon-6208
09/30/2019, 8:13 PMambitious-helmet-24352
09/30/2019, 8:35 PM--enable-ip-alias
on GKE to deploy a private cluster ?busy-umbrella-36067
09/30/2019, 8:48 PM@pulumi/kubernetes
?
apps/v1beta1/Deployment is not supported by Kubernetes 1.16+ clusters. Use apps/v1/Deployment instead.
acceptable-army-69872
09/30/2019, 10:07 PMawsx.ec2.Vpc
use this array of AZs? or am i stuck building out the subnets by hand?colossal-room-15708
09/30/2019, 10:54 PMcolossal-barista-38672
10/01/2019, 2:24 PMfresh-flag-12765
10/01/2019, 2:35 PMpulumi up
just hangs with:
I1001 10:33:50.904083 58684 eventsink.go:63] eventSink::Debug(<{%reset%}>Trying to get account information via sts:GetCallerIdentity<{%reset%}>)
I1001 10:33:51.051500 58684 eventsink.go:60] Trying to get account information via sts:GetCallerIdentity
I1001 10:33:51.051533 58684 eventsink.go:63] eventSink::Debug(<{%reset%}>Trying to get account information via sts:GetCallerIdentity<{%reset%}>)
I1001 10:33:53.097326 58684 api.go:193] Making Pulumi API call: <https://api.pulumi.com/api/stacks/<snip>/events/batch>
I1001 10:33:53.219992 58684 api.go:209] Pulumi API call response code (<https://api.pulumi.com/api/stacks/<snip>/events/batch>): 200 OK
Seeing the same behaviour across two different machines. Any ideas?fresh-flag-12765
10/01/2019, 2:48 PMpulumi refresh
worked finefresh-flag-12765
10/01/2019, 6:01 PM