-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom provider support #24
Comments
any progress on this, Jye? |
Absolutely, thanks for checking in. The providers previously were baked directly into our CLI, they have now been separated so they can be downloaded and run independently. Since they communicate using gRPC, new providers can now also be written in languages other than Go, which we're hoping is helpful for teams using languages like TypeScript or Python to build custom solutions. The first cut of the documentation on this functionality is here. This documentation could be hard to follow since the Nitric contributors are the only people who've really worked on providers at this stage. We'd be happy to provide assistance or guidance if anyone wants to start building their own providers or contribute to the existing providers. We'll update the docs in turn to reflect what we learn from providing that help. @tjholm also built a recent prototype provider that uses Terraform to deploy to AWS. It currently doesn't support all of the Nitric resources and requires a custom step to build containers, but we'd be happy to let you take a look if that would be useful. Otherwise, our existing Pulumi based providers are a good place to start. |
@geoman2 do you have a specific resource that you'd like to build a custom provider for? This is an area we'd like to put more focus on, so anything you can share would help us refine requirements. |
Scaleway and cloudflare integration would be nice to have |
@geoman2 thanks for the response, those are good suggestions. Couple of followups -
|
summary
Allow developers to build their own implementations of Nitric providers and use them with the Nitric CLI.
intended outcome
Allows for full custom provider development, where Nitric framework users can take full control of their deployment process or customize an existing provider.
The text was updated successfully, but these errors were encountered: