This message was deleted.
# general
s
This message was deleted.
b
we only currently support native providers in Go
c
ah right ok thanks
So for interfacing with a SAAS would a component work, or are they specifically for extending existing providers?
Basically we are looking to do things that the existing github provider doesn't do around organizations. We already have a provider written in python that is working that we can call from the local fs
Were just wondering what the best way to package it was for re-use
b
you want a dynamic provider for that, if you’re using typescript or python
We already have a provider written in python that is working that we can call from the local fs
interesting, does this interface with the enginer via grpc?
c
Yeah sorry I should have mentioned it was a dynamic provider at present
that we were hoping to make more re-usable
but if that's not supported we can just do filesystem import
Is pretty basic code
b
we don’t have a mechanism to repackage dynamic and distribute dynamic providers just yet, so a filesystem import is likely your best bet
c
Ok no worries. Thanks heaps for the info, saved me a tonne of time!
e
Note that we will be supporting full providers in all our languages soon, https://github.com/pulumi/pulumi/issues/10915 is tracking this for typescript.
c
Awesome thanks