works 🙂 wasn't sure about the

pulumi config set password

part

Any plans to support Google Cloud Run? Managed containers 🙂

or is this already supported?

https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/attend/novel-coronavirus-update/ No KubeCon Amsterdam next month. 😢

Gotta say the GKE price increase is kind of messed up.

what is the GKE price increase?

Quick question, is there any simple way to user the

data

inside the ConfigMap to get all the keys in typescript. Need these to make the volume mounts with keys instead of the hole folder.

Wondering if anyone can help me out. I am having a weird issue with my state. My coworker and I are getting different preview output. We are both on the master branch and the same commit hash, but he has 27 things to change and I have only 4. Is there cache or something else that he isn't getting the latest state? From the console I can see we are previewing the same stack, but we are getting the different results.

Most pulumi commands suddently started hanging for me - ie

pulumi version

will work, but

pulumi stack ls

will hang indefinitely. tried increasing verbosity but I'm not getting any extra logs of value - ideas?

I'm trying to identify what the "policy" object of aws.kms.Key should look like. It appears to want JSON (error: "policy" contains an invalid JSON: invalid character 'a' looking for beginning of value), but all of the options I've tried (including ones from AWS' documentation) produce errors either in my IDE or when I run pulumi up (error: "policy must be a single value, not a map"). Where can I find an example of syntax the policy object this item is expecting?

class pulumi_aws.s3.Bucket(resource_name, opts=None, acceleration_status=None, acl=None, arn=None, bucket=None, bucket_prefix=None, cors_rules=None, force_destroy=None, hosted_zone_id=None, lifecycle_rules=None, loggings=None, object_lock_configuration=None, policy=None, region=None, replication_configuration=None, request_payer=None, server_side_encryption_configuration=None, tags=None, versioning=None, website=None, website_domain=None, website_endpoint=None, __props__=None, __name__=None, __opts__=None)

In this if I pass resource_name as "mybucket" then it create s3 bucket with name "mybucket-677282" is it any way to create bucket with my bucket only. Or any one can suggest me this have policy field so if I pass policy in that "resource" needs the ARN of bucket which is not created with a single call how I can create bucket with attached policy.

hi everybody, I am trying to write some unittest (writing python) but after enabling test mode I get this error

pulumi.errors.RunError: Missing project name; for test mode, please set PULUMI_NODEJS_PROJECT

I tried to set both PULUMI_NODEJS_PROJECT and PULUMI_PYTHON_PROJECT but it seems the project name is not picked up anybody knows how can I solve this issue?

for know the only workaround I found was to import

_set_project

from pulumi.runtime.settings

but I don't feel it's the way to go

Does Pulumi support Google Cloud Run?

ah, I found it: https://www.pulumi.com/blog/google-cloud-run-serverless-containers/

is there a way to call

pulumi up

programmatically? (i.e.: I have an http rest service to create resources)

How far do you guys take your microservices? I got tired of building a seperate microservice for every single freaking thing and I consolidated most of mine. It got to be a massive pain in the ass to troubleshoot when i had a micro for literally everything...

monitoring & metrics are key for having many microservices tbh

Personally, I prefer building a monolithic app first. It gives me the opportunity to see what the notable aspects of the application are, which can then be transitioned to microservices if it makes sense to do so. Trying to predetermine how everything ought to be separated can be tricky.

Microservices make things more complicated, which is bad. They only make sense if they remove enough other pain (like being able partition code that a dev needs to know and hand it over to different, specialized teams) to balance the cost of complexity. For most companies time for microservices is going to be no earlier than after dev team exceeds 50 people.

I think most orgs are using microservices as a way to organize their workforce and limit blast radius, however there are some systems where monoliths end up being resource inefficient and have to be over-scaled. For example, if there is a really CPU intensive but infrequent workload, you may have to run more instances to support it that end up being mostly idle. Those are good places in a monolith to hand off to a workers, so the main app can run efficiently and consistently and the worker pool can scale separately. Those worker tasks can turn into microservices as needed, but don't have to. Microservices from the ground up has a lot of cognitive/tooling overload. I've thought its kind of silly to try to improve a system's overall reliability and TCO by simply adding 10X more network requests 😛

hey does anyone know / is it possible to gracefully cancel a job in circleci (without leaving the pulumi state in a broken state) ?

Hello 👋, Is there any code example on how to use the new mocking feature?

Is there a way to change an account created via a Github-Login to an email one?

Hello

Does Polumi support Azure partner customer usage attribution (https://docs.microsoft.com/en-us/azure/marketplace/azure-partner-customer-usage-attribution)?

Anyone have an opinion on doing a resource per file or grouping resources into a “component” file? For example, if I have a project deployed to kubernetes. We have the

Deployment

, several `CronJob`s,

Service

,

VirtualService

(istio),

HorizontalPodAutoscaler

,

PodDisruptionBudget

, a CloudSql database, database users, etc. Would you recommend: * app.ts (contains the resources deployed to kubernetes, AKA, the “application”) * database.ts (contains the resources to create the database and the users * index.ts (requires the other 2 Or would you recommend: * app/deployment.ts * app/virtualService.ts * app/podDisruptionBudget.ts * cronJobs/cronJob1.ts * database/instance.ts * database/user1.ts

Hello 👋, Can you specify in Pulumi that you want to depend for one resource on all sub-resources of a ComponentResource to be ready? For example, I want to create an Istio service mesh, want to wait until all the things are ready, and then launch the rest of the pods. Happy to hear suggestions or patterns. :)

Hi y’all! I could use some thoughts on best practices for stacks and projects. My project consists of DynamoDB, Lambda, an S3 bucket, and a few other tidbits. While they are part of the same overall project, they will be versioned independently and might be worked on by different teams. Ideally I don’t want to deploy the entire project if a simple change is made to the S3 bucket (or more commonly to Lambda). The project also needs to exist in several environments (dev, staging, prod). So how should I create my project(s)? • Do I create a project for each group of resources and stacks for the environments (like lambda/dev and s3/prod) • Do I create a project for the overall project and name my stacks based on resource type and environment (like project acmeserverless and stacks lambda-dev and s3-prod) • Something else that I haven’t thought of