Teams leave SaaS configuration outside Terraform when providers have gaps
The reports describe missing Terraform resources for GitHub OAuth and GitHub Apps, Datadog integrations and notebooks, and Azure AD B2C applications. In one case, a service principal has to be created manually before Terraform can create the B2C application; the other reports establish resource gaps but do not describe a consistent workaround. Any product would need to support each service’s API, and some objects may not expose APIs that allow full lifecycle automation.
For platform and infrastructure engineers. Mentioned from Feb 2020 to Oct 2024 on GitHub.
8 different people described this problem in 6 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 5.0/10
- Frequency
- 7.9/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
We are working on some frontend react integrations with terraform code. Where in we want to provision application and then create on github oauth application. All above is with terraform
I would like to have this implemented to create rancher clusters with terraform where user can authenticate via github
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 3 places to find your first customers
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks