This message was deleted.
# general
s
This message was deleted.
g
I did mostly for my own use and for use in my company: https://www.npmjs.com/package/pulumi-gcp-components
👀 1
a
1. When you released those packages did you build them to javascript or leave them as typescript for pulumi to build. 2. Would you do it again?
g
1. Since they are npm dependencies you need to transpile them to JS 2. We have a few more internally to share across projects, if possible yeah I would make more components public
You are welcome to send more components or give ideas of what you need in the repo so I can make some more generic components
a
Awesome! This is really helpful to see your setup.
I'm in the same boat about being limited what I can make public.
g
I've sent a few times on gcp and typescript channel a component to setup a whole project (appengine, firebase region, credentials and provider). I'll probably add it to this repo, everything specific for our use case was already factored out
a
One thing I'm working on is a module that sets up a cloud run scheduled job given a docker image and schedule (it does all the service accounts, IAM, and other boilerplate)
g
There is a scheduledFunction component in the repo, you can check it out
🙌 1
👀 1
l
awsx is a pretty extensive example of what you're describing in terms of higher level cloud components. https://github.com/pulumi/pulumi-awsx
g
Yeah I made my own set exactly because there is no gcpx yet. Would have contributed to it otherwise.