does the fact that the automation api is written i...
# automation-api
b
does the fact that the automation api is written in go mean it can only load projects written in go?
l
Not at all. You can use a local project on disk written in another language, or a project in a git repo written in another language. For instance a local program on disk: https://github.com/EvanBoyle/automation-api-examples/tree/main/local_program It uses this pulumi program, but you could replace it with one written in any language: https://github.com/EvanBoyle/automation-api-examples/tree/main/local_program/fargate
This program uses an example from the pulumi examples repo: https://github.com/EvanBoyle/automation-api-examples/blob/main/git_repo_program/main.go#L24-L27 But you could easily change the project path to use one written in typescript, python, etc.
b
awesome, i was hoping that was the case! thanks for the response.
l
What other languages are you planning on using with it?
b
probably typescript -- i have some projects written in ts. we're still trying to decide as a team what deployment tech we want to go with (terraform vs pulumi)
l
Cool, typescript support is a (rough) work in progress: https://github.com/pulumi/pulumi/pull/5347
b
yeah i saw that you guys wanted to add support for other languages. we don't have anyone who knows go, but we do have some knowledge of python and ts. if it's just a single thing that loads up a
dependencies.json
, and runs those remote projects recursively, that's probably not too bad.
l
Great, I'll let you know when typescript support is ready to try out. We need to do an internal review over the API shape, but it's already functional. I got inline programs working today, here's an example of usage: https://github.com/pulumi/pulumi/blob/f23011170461af0243fd230a1e5494790a30d59f/sdk/nodejs/tests/automation/localWorkspace.spec.ts#L191-L235