Pulumi support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
It would be nice if we could write Pulumi / Terraform code to describe a Dokploy configuration, and it would automatically sync with it, so we could really have "infrastructure as code", with the benefit of having the nice Dokploy UI for monitoring and to access containers when needed!
Perhaps Pulumi could target each Dokploy project, so we could have a Pulumi for "production", a Pulumi for "staging", and then use Dokploy "manually" in a "apps" project when we need ad-hoc stuff that we don't want to add in the Pulumi code?
Describe the solution you'd like
A way to script the Dokploy API through Pulumi
Describe alternatives you've considered
Do a script to run Dokploy CLI deploy commands, but that defeats the purpose, since the cool thing about Pulumi is that it "synchronizes" a "description of the infra", rather than doing "imperative commands"
Additional context
No response
Will you send a PR to implement it?
Yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by reviewing the Dokploy API and how a Pulumi provider could represent Dokploy projects and resources. Use the production, staging, and ad-hoc apps examples as the initial scope, and define synchronization behavior before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- terraform
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100