-
Notifications
You must be signed in to change notification settings - Fork 5
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
story: explore use cases for data resources #92
Comments
We'd definitely be interested in data sources being implemented. Our particular use-case is that each of our services have their own TF codebases defining the service and all associated resources. We want to include check definitions there as well. The issue arises that the check resource requires IDs rather than names, so for use of snippets, alert channels, groups that are shared across multiple services (e.g. one dev team with multiple services) we don't have the ability to easily interrogate the API for those IDs. For the time being we have a central Checkly repo that defines all the snippets, groups and alert channels and are then using the remote state data resource in the service repos to get IDs |
@benfielden-onx, thanks for your feedback, it's really useful. I can't tell you when we are going to start working on this but is definitively on our radar. |
Some possible use cases for data sources
The text was updated successfully, but these errors were encountered: