set the channel description: 2.0 Hackathon!

Can I submit an existing project? 😂

set the channel topic: Kickoff Zoom (9:30AM PDT 3/19): https://zoom.us/j/608276296?pwd=WnVKcWl1WEE3L3pHZkxqL244b216QT09 Demo Zoom (5PM PDT 3/19): https://zoom.us/j/250621391?pwd=UnlsR0RUbVFMaS9tNlk5aGpOVjJrZz09

@green-morning-1318 sure! 😄 . Though it's not so much a "submit" kind of thing as a "work on" and "share" thing. Feel free to share details here about the project you are going to be working on (even if it's something you are already working on), and to join us for kickoff and demo sessions on Thursday!

Thanks @white-balloon-205 😁 I’m kinda working on two things. • AWS SAM allows you to choose from a list of policy templates to scope the permissions of your Lambda functions to the resources that are used by your application. Pulumi doesn’t have this functionality (which I understand by the way), so I built a Go module for it: https://github.com/retgits/pulumi-helpers. My idea for this one is to create “helper” methods for things I frequently need to do, which might simplify my code and speed up development even more. • The team I’m in built a Fitness shop as demo app and I built a serverless version based on that. Most of the deployments are done with Pulumi: https://github.com/retgits/acme-serverless (this is the main repo, all services have their own repo).

Whaaaaat? This is awesome

Now if only someone could hook me up with a sweet CircleCI account I could add CI/CD in there too 😏

Here’s a simple project to get started for folks wanting to hack on the Go k8s SDK. I included a README.md file in the folder with instructions and caveats.

I'm not sure if I'll have the time but I wanted to suggest a topic for this Hackathon : Slack doesn't have an API for creating a Workspace, and so this step needs to be done manually everytime so that you can get an API key and then use the official API to perform chat automation (AKA ChatOps) My idea is that if you use the Chrome Debugger and create a Slack Workspace, it's easy to reverse-engineer the POST request that goes to their servers (I have the URL & payload if you need it) This POST request is actually a public API, so it can be wrapped via Pulumi in a Dynamic Provider ! So my project is a proof-of-concept of that : making a Pulumi Dynamic Provider for any HTTP API (showcased via Slack) If you're interested in collaborating, feel free to reply to this thread and I'll share the details of what I have so far 🚀

If anybody wants to give testing a try, this PR has basic examples of mock-based unit testing in all four runtimes, as well as a Policy-as-code testing example in TypeScript: https://github.com/pulumi/examples/pull/608

Join the Hackathon Kickoff meeting now at https://zoom.us/j/608276296?pwd=WnVKcWl1WEE3L3pHZkxqL244b216QT09 (also pinned to channel).

Here’s some information on trying out Python policies (thread)

I’ll be using the new Go SDK for k8s to port some popular 3rd party services. If anyone else is working on k8s work and has questions or needs another pair of 👀 , happy to help

Today I will be working on adding the new policy as code configuration model into AWSguard, our collection of policies for AWS resources.

Originally, I wasn’t sure how to make the ‘chaos monkey’ idea work. I wanted to bring in the resources and run my test code in the same application, but couldn’t think of a way to make that work. Because after you import a resource, you can’t change it again in the same run. Then I remembered there’s

EditDirs

in

ProgamTest

, which lets you apply multiple steps. So now I’m thinking the way this would work is you take an existing Pulumi application as the first step, then subsequent steps are additive updates to modify the resources. And the tests would occur within each step (or potentially

ProgramTest

itself). But thinking through this, I’m not sure this is actually any kind of improvement over writing directly against the provider APIs. Thoughts on if this ergonomically seems useful? I do like the idea of the fact that with each step, the state of your infrastructure is quite clear (vs writing a bunch of API calls to modify resources).

If anyone is interested in the ongoing work on our Go SDK, and would be interested in playing with code generation, then this might be a fun hackathon issue to look at: https://github.com/pulumi/pulumi/issues/3861

I want to participate but I got this thing called work for the next 2 hours but I'll be back later

ready to hack!

priorities Angel 🙄 😂

Hi team, is there any way to debug / troubleshoot why my

pulumi up

command is “hanging”? It doesn’t look like anything is happening 😞

Debugger attached to Pulumi TypeScript program!

Alright!! Created 166 resources through Pulumi… Among them 24 Lambda Functions, 4 API Gateways, 6 SQS Queues, and 1 S3 Bucket

pulumi preview

errors in VS Code!

message has been deleted

I just got my configurable policies to a good spot. The policies are checking for instance classes that are used (e.g.

t3.medium

) and the total number of instances in my stack. Here's output with policy violations with "DEV" config. The same code passes with no violations with my "PROD" config that allows for different instance classes and more instances (in thread).

I won’t be able to make it to the demos 😞 Hoping to hear about all the awesome things people hacked on though! I kind of got a rejiggered version of

ProgramTest

working the way I would think you’d want to do some kind of chaos testing. But I was trying it on the service stack, which has a decently long preview time, and I’m not sure this is how I’d want to actually do this type of testing in practice.

ok, probably should have factored in day full of meetings, podcasts, etc when scoping this 😆 However, baby steps

package main

import (
	"<http://github.com/pulumi/pulumi-kubernetes/sdk/go/kubernetes/yaml|github.com/pulumi/pulumi-kubernetes/sdk/go/kubernetes/yaml>"
	"<http://github.com/pulumi/pulumi/sdk/go/pulumi|github.com/pulumi/pulumi/sdk/go/pulumi>"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := yaml.NewConfigFile(ctx, "guestbook",
			&yaml.ConfigFileArgs{File: "guestbook-all-in-one.yaml"},
		)
		return err
	})
}

Can you run this against any K8s cluster?