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

is there a way to make a pulumi run wait if there's an operation underway? other than some hacky bash...

I’m trying to use

pulumi preview -t urn:xxx --target-dependents

where

xxx

is the parent of some subset of my stack, but I’m getting an error:

Cannot delete parent resource `xxx` without also deleting child `yyy`

I would have thought

--target-dependents

would fix that. Am I missing something or is this possibly a bug?

Hello! New pulumi user here considering to move over from terraform. I'm trying to set up a very trivial configuration and I'm already stuck. Consider the following tenliner: https://gist.github.com/farcaller/deadd9cb5375549037d1de0f5479a623. I have a list of repositories to manage. Pulumi works perfectly and imports both. Now, if I change the order of items in the

repos

pulumi suggests it needs to re-create both repos because their order changed. Clearly, my repos aren't keyed by index but by their names. In terraform I'd use

for_each

over a set. How do I achieve the same in pulumi?

I'm trying to run

pulumi plugin install

in a shell-script, but this won't do anything. Running the same command in the same directory in the terminal installs the current aws resource plugin. Any idea on how to make this command work in a script without specifying the exact plugin to install?

Hi, I'm trying to destroy a stack that consists of an AWS API Gateway with a lambda and some static files behind it; when I run

pulumi destroy

I get a failure:

Do you want to perform this destroy? yes
Destroying (ng-dev):
     Type                          Name               Status                  Info
     pulumi:pulumi:Stack           devng-ng-dev       **failed**              1 error
 -   └─ aws:apigateway:Deployment  normalgaussiandev  **deleting failed**     1 error
 
Diagnostics:
  aws:apigateway:Deployment (normalgaussiandev):
    error: deleting urn:pulumi:ng-dev::devng::aws:apigateway:x:API$aws:apigateway/deployment:Deployment::normalgaussiandev: error deleting API Gateway Deployment (855quj): BadRequestException: Active stages pointing to this deployment must be moved or deleted
 
  pulumi:pulumi:Stack (devng-ng-dev):
    error: update failed

… (message deleted)

Hi All, Hope you know this issue. I'm trying to create an API for Azure Api management with import the definition from the swagger json file. However I got error is Parsing error(s): The Swagger version specified is unknown. However, I'm able to import the file to Api management manually.

// Create the API definition and map it to the HTTP Function backend
  const api = new azure.apimanagement.Api(name, {
    name,
    resourceGroupName: apimInfo.group,
    apiManagementName: apimInfo.name,
    displayName: displayName || name,
    import: autoImport
      ? {
          contentFormat: 'swagger-json',
          contentValue: fs.readFileSync(`./${env}-api.json`, 'utf8')
        }
      : undefined,
    path: apiSuffix || '',
    protocols: ['https'],
    revision,
    serviceUrl
  });

Is there any way to use manged appservice certificates with pulumi? What I mean is to just create them on the fly.

Anyone knows how to configure the container port for Cloud Run via Pulumi?

Can I just set the

PORT

env variable?

is it possible using Pulumi to build from a Dockerfile and then run a docker container with the built image, all locally? All my attempts failed with problems related to docker registry. It seems that

@pulumi/docker

requires me to have a proper docker registry running (which I would like to avoid for dummy localhost deployments). I even started setting up a local docker registry in my machine, but the struggle to setup TLS and authentication on it made me think that there must be an easier path for this 😕

Can CrossGuard somehow work when not using the service?

Hi all, Sorry if this has been answered already but regarding the workshop in Amsterdam https://www.pulumi.com/events/workshop-amsterdam-2020-03-30/ Has it been cancelled?

is top level await in typescript supported?