Title
a

adventurous-wire-92385

06/29/2018, 11:52 PM
Is there an equivalent term for "chart" in pulumi? For example if I were making a contained component for Nginx-Ingress or something? "pulumi-module-nginxingress"?
b

big-piano-35669

06/30/2018, 11:09 PM
We typically just create packages for such things, e.g. NPM in JS/TS. Our AWS infrastructure package is a good example: https://github.com/pulumi/pulumi-aws-infra. The Jenkins component in our examples repo could have easily been turned into one -- and probably should be as a nice example of how to go about this -- and was sourced from one of the Bitnami charts: https://github.com/pulumi/examples/tree/master/kubernetes-ts-jenkins
So in a nutshell, I'd just call these "packages."
a

adventurous-wire-92385

07/01/2018, 1:42 AM
So if I were packaging
nginx-ingress
just
pulumi-nginx-ingress
? I didn't know if there was a hope to keep
pulumi-*
be for official pulumi packages and
pulumi-[chart|k8s|some-other-term]-*
for user-packaged things for the kubernetes ecosystem. I might just be over-thinking naming 🙂.
b

big-piano-35669

07/01/2018, 7:10 PM
These are good questions. I wouldn't say we have a strong answer here, partly still learning what works. For instance, the
@pulumi
packages were exactly what you say, officially sanctioned packages. I do feel like having a clear naming convention here will help: one of the strengths and weaknesses of our system is that things are "just" packages. @white-balloon-205 @creamy-potato-29402 Any thoughts?
c

creamy-potato-29402

07/01/2018, 9:15 PM
It’s a good question that I don’t have a good answer to. I don’t think there’s a need to reserve
pulumi-*
for official packages though…