worried-city-86458
09/27/2019, 5:03 AMwarning: extensions/v1beta1/PodSecurityPolicy is not supported by Kubernetes 1.16+ clusters. Use policy/v1beta1/PodSecurityPolicy instead.
limited-rainbow-51650
09/27/2019, 8:04 AMCreate > Deploy > Manage
section of the front page?fancy-translator-86814
09/27/2019, 9:55 AMpulumi up
, I got notification for update:
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.
but in actual, when I run brew upgrade pulumi
,
$ brew upgrade pulumi
Error: pulumi 1.1.0 already installed
This is a bit annoying. Is this lag comes from brew?
Is it possible not to show this update message?worried-musician-21478
09/27/2019, 12:26 PMstale-park-1622
09/27/2019, 2:08 PMexport function createApiImage(name: string, port: number, contextDir: string): {repositoryUrl: pulumi.Output<string>, image: awsx.ecr.RepositoryImage} {
const gitCommit = 'e0e5162';
// set up ECR Lifecycle Policies (<https://docs.aws.amazon.com/AmazonECR/latest/userguide/LifecyclePolicies.html>)
// remove any images that are older than one week that are untagged
const repository = new awsx.ecr.Repository(`pulumi-${pulumi.getStack()}-repository`, {
lifeCyclePolicyArgs: {
rules: [{
selection: "untagged",
maximumAgeLimit: 7,
}],
}
});
// And publish its URL, so we can push to it if we'd like.
const repositoryUrl = repository.repository.repositoryUrl;
const build: docker.DockerBuild = {
context: contextDir, // context is a path to a directory to use for the Docker build context
dockerfile: path.join(contextDir, './docker/api.v2.Dockerfile'), // dockerfile may be used to override the default Dockerfile name and/or location
args: {
EXPOSE_PORT: String(port),
},
};
// Invoke 'docker' to actually build the DockerFile that is in the folder relative to
// this program. Once built, push that image up to the ECR repo.
//const image = repository.buildAndPushImage(build);
const image = awsx.ecr.buildAndPushImage(
`${name}:${gitCommit}`,
build,
{
repository: repository.repository,
}
);
return {repositoryUrl, image};
}
→ pulumi up
Previewing update (dev):
Type Name Plan
+ pulumi:pulumi:Stack dev create
+ ├─ awsx:ecr:Repository dev-api-image:e0e5162 create
+ │ └─ aws:ecr:LifecyclePolicy dev-api-image:e0e5162 create
+ └─ awsx:ecr:Repository pulumi-dev-repository create
+ ├─ aws:ecr:Repository pulumi-dev-repository create
+ └─ aws:ecr:LifecyclePolicy pulumi-dev-repository create
Resources:
+ 6 to create
Do you want to perform this update?
yes
> no
details
flat-guitar-86436
09/27/2019, 5:39 PMstale-park-1622
09/27/2019, 5:45 PMconst image = awsx.ecr.buildAndPushImage(
`${name}:${gitCommit}`,
build,
{
repository: repository.repository,
}
);
it always add the 'latest' tag. I want to tag it with a git commit hash. Is there a function like 'tagAndPushImage'?damp-book-35965
09/27/2019, 5:52 PMbillowy-laptop-45963
09/27/2019, 6:30 PMbrash-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
brave-angle-33257
09/30/2019, 6:49 PMgoogle-protobuf
Diagnostics:
pulumi:pulumi:Stack (api-ecs-services-us-east-2-dev-auth):
error: Running program '/data/pulumi/infra/aws/api/api-ecs-services' failed with an unhandled exception:
AssertionError: Assertion failed
at new goog.asserts.AssertionError (/data/pulumi/node_modules/google-protobuf/google-protobuf.js:79:876)
at Object.goog.asserts.doAssertFailure_ (/data/pulumi/node_modules/google-protobuf/google-protobuf.js:80:257)
at Object.goog.asserts.assert [as assert] (/data/pulumi/node_modules/google-protobuf/google-protobuf.js:81:83)
at jspb.BinaryEncoder.writeDouble (/data/pulumi/node_modules/google-protobuf/google-protobuf.js:329:67)
at jspb.BinaryWriter.writeDouble (/data/pulumi/node_modules/google-protobuf/google-protobuf.js:351:300)
at proto.google.protobuf.Value.serializeBinaryToWriter (/data/pulumi/node_modules/google-protobuf/google/protobuf/struct_pb.js:383:12)
at jspb.BinaryWriter.writeMessage (/data/pulumi/node_modules/google-protobuf/google-protobuf.js:353:336)
at jspb.Map.serializeBinary (/data/pulumi/node_modules/google-protobuf/google-protobuf.js:274:356)
at proto.google.protobuf.Struct.serializeBinaryToWriter (/data/pulumi/node_modules/google-protobuf/google/protobuf/struct_pb.js:189:7)
at jspb.BinaryWriter.writeMessage (/data/pulumi/node_modules/google-protobuf/google-protobuf.js:353:336)
white-balloon-205
09/30/2019, 7:31 PMbrave-angle-33257
09/30/2019, 11:26 PM