Yeah, I've been trying to get pkg working with aws-cdk. I'm hoping it'll be simpler with pulumi

https://docs.appimage.org/packaging-guide/manual.html#ref-manual 🤷

Welcome to the wonderful world of software distribution ;)

On the other other other hand, there's https://fpm.readthedocs.io/en/latest/intro.html

Oh yeah, I've used fpm before, forgot about that

but I don't want to install 'things' on people's systems

the idea is to just get an aws env set up

but saying "Install docker first" is probably the best I can do

Hi, would anyone know some articles on how to organise infra and deployments into projects and stacks? specifically talking about a general purpose k8s kluster for our organisation that would need to host multiple deployments of application services. I’ve read (somewhere) a pulumi stack can pull in infrastructure managed in a different repository, which sound what I would need…

Hi all, I'm considering writing a custom provider but wonder whether this has to be written in Go or if that's also possible in TypeScript and if so if there is an example of a TS based provider. I used dynamic providers previously but feel that they are not really reusable across projects...

I’m experiencing pretty slow

pulumi up

runs (even during preview phase) with a project containing two `StackReference`s. It’s hanging on

running     read pulumi:pulumi:StackReference ajaegle/proj/stack

for ages and the super verbose log doesn’t list any more lines than the ones that were there since the beginning (the diff of some resources). I don’t expect that to be lossy internet connectivity as my machine is constantly using almost two cores for the pulumi process.

I have a chicken and the egg kind of question. Let’s say that you have some applications that you want to run on a kubernetes cluster. The images should be published to a registry first and that is something I would like to do during build, but the registry isn’t created until deployment. Is there a best practice here? Setting up the registry in its own project?

Is there a way to create an object that only exists to get a name with a suffix (to break circular dependencies)? If you want to make a storage container that's only accessible from a web app that knows the name of that storage container, then you need to make the container with a CORS rule that knows the URL of the web app, but the web app needs to know the deployed name of the container. If you can create a placeholder resource that gets the suffix added to its ID, then the web app can be given the ID, and the container can then be created with that name and a CORS rule with the URL of the web app. like:

let containerIdHolder = CustomResource("justAName", "mycontainer", ResourceArgs.Empty)
...
let envVars = Inputs.ServiceTemplateSpecContainersEnvsArgs(Name = "containerName", Value = containerIdHolder.Id)
...
let webApp = WebApp (envVars = ["containerName", containerIdHolder.Id)]) 
...
let actualContainer = Container (Name = containerIdHolder.Id, CorsRules = (Origins = [webApp.url]))

Is that possible?

https://onalytica.com/blog/posts/top-100-cloud-influencers/?ck_subscriber_id=512829154 Wow Joe is 23rd ❗

until the bug with

runtime.listResourceOutputs

is fixed, are there any suggestions from folks on what i could use in the interim? i'm using it to, if no resource X has ever been deployed, deploy it, otherwise, use what's already deployed.

Deployment name is appended with random chars when used like this - https://github.com/grendach/pulumi-quickstart/blob/61911bc3cb2464c58c4e64d75a1c0e0980e40d79/__main__.py#L14 -- Any tip to fix it ?

Is there a way to have global value with stacks? I don’t want to copy the same value in my multiple stack?

I literally just came here to ask the exact same question @big-potato-91793

Is there some known issue with deletion of objects from Pulumi stacks not working when we perform a partial update with

pulumi up --target=xxx

? In one of our stacks, I always get an error similar to

Target 'urn:pulumi:<pulumi-stack-name>::<pulumi-project-name>::gcp:dns/recordSet:RecordSet::cname-dev' could not be found in the stack. Did you forget to escape $ in your shell?

I have been careful to ensure that there's no

$

in the URN name as the error message seems to suggest. The reason I need to perform such partial updates is that one of the objects in this Pulumi stack is a GCP VPC private subnet, whose metadata gets updated on a vanilla

pulumi up

, but then Pulumi can't update this subnet URN since it's already being used by a GKE cluster.

I would like to specify a log group name for this callback function on an API Gateway route, but there doesn't seem to be a property available to do so.

const apiGateway = ( queueIDObject ) => {
    return new awsx.apigateway.API( GATEWAY_NAME, {
        routes: [ {
            path: ROUTE,
            method: 'POST',
            // Note wrapping this as a callback function it can have additional attributes set on the lambda
            eventHandler: new aws.lambda.CallbackFunction("write-event-to-sqs", {
                memorySize: 128,
                callback: async ( event, context ) => {
                    return webhookProcess.fire( event, context, queueIDObject );
                },
            description: "write events to queue and return 200"
            })
        } ]
    } );
};

Any ideas on how I could get

eventHandler

logs written to a named log group?

Hi. I have some questions regarding the tf2pulumi tool. Could you please help me with that? 1. Is Terraform 0.12 still not supported? 2. Does the tool support only 2 "output" languages (TS and Python)? 3. From what folder exactly should I run tf2pulumi? I'd like to convert from

terraform/variants/webapi-dev/webapi-dev.tf

to

pulumi/index.ts

.

├── pulumi
│   ├── Pulumi.yaml
│   ├── index.ts
└── terraform
    ├── README.md
    ├── modules
    │   ├── shared
    │   │   └── <http://main.tf|main.tf>
    │   └── webapi
    │       └── <http://main.tf|main.tf>
    └── variants
        ├── shared
        │   └── <http://shared.tf|shared.tf>
        ├── webapi-dev
        │   └── <http://webapi-dev.tf|webapi-dev.tf>
        └── webapi-prod
            └── <http://webapi-prod.tf|webapi-prod.tf>

Is there a REST API for retrieving data from my Pulumi stacks? I have some secrets/resources stored there that I’d like to access with`curl`

I’ve been able to access stack exports, but can’t figure out how to decrypt secrets from the REST API, since I can’t find documentation for it

Hi, is there a documented process on how to upgrade the provider plugins for a specific stack?

I previously created some secrets using

pulumi config set --secret …

Now I want to remove those so I can run the stack from a different location. Just clearing them out of my local config file didn’t seem to do anything

Hey is anybody having a hard time reading AWS docs in Chrome recently? I can't seem to scroll down or expand the sidebar, and have to hop into Firefox to read them. It just started this week, and I don't believe I added any browser extensions that could have borked anything.

Have any guidelines/suggestions been created for using the S3 state backend WRT organizing projects and stacks? I've read https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/ but it seems to focus only on using Pulumi as the state backend.

Hi, I'm running into an issue when trying to run

pulumi up

I am getting the following error

error: deleting urn:pulumi:production::insig-express::awsx:x:ecs:Cluster$awsx:x:autoscaling:AutoScalingGroup$awsx:x:autoscaling:AutoScalingLaunchConfiguration$aws:ec2/launchConfiguration:LaunchConfiguration::apps-autoscaling-prod: error deleting Autoscaling Launch Configuration (app-autoscaling-prod-9341984): ResourceInUse: Cannot delete launch configuration app-autoscaling-prod-9341984 because it is attached to AutoScalingGroup app-autoscaling-prod-654d7a2-Instances-10K7OFBLTHZ2N

  

status code: 400

I've tried everything on this page https://www.pulumi.com/docs/troubleshooting with no luck. Any advice would be appreciated!

Say I have a stack that depends on the output of another stack. when I update the parent stack and the output changes, what is the “best practice” way to cascade changes down to all dependent stacks? currently it seems i need to go and manually run updates in all dependant stacks. the documentation mentions “cascading updates”, is there some other way of managing this? https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/#inter-stack-dependencies

Hi, thanks for a quick addition of fargate option for EKS. I'm trying that out with code from the example and i'm getting errors around pod creation. Is it some issue with routing, or something to setup beforehand? Thanks!

kubernetes:extensions:Deployment (kube-system/monitoring-influxdb):
    warning: extensions/v1beta1/Deployment is deprecated by apps/v1/Deployment and not supported by Kubernetes v1.16+ clusters.
    error: 2 errors occurred:
    	* resource kube-system/monitoring-influxdb was successfully created, but the Kubernetes API server reported that it failed to fully initialize or become live: 'monitoring-influxdb' timed out waiting to be Ready
    	* Minimum number of Pods to consider the application live was not attained