Skip to content
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

Open
ianaya89 opened this issue Nov 10, 2021 · 2 comments
Open

story: explore use cases for data resources #92

ianaya89 opened this issue Nov 10, 2021 · 2 comments
Assignees
Projects

Comments

@ianaya89
Copy link

ianaya89 commented Nov 10, 2021

Some possible use cases for data sources

  • locations
  • runtimes
  • existing data created from dashboard (checks, envs, snippets, etc)
@ianaya89 ianaya89 added this to To do in Maintenance Jun 13, 2022
@ianaya89 ianaya89 changed the title Explore use cases for data resources story: explore use cases for data resources Jun 13, 2022
@benfielden-onx
Copy link

benfielden-onx commented Jul 28, 2022

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

@ianaya89
Copy link
Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Maintenance
  
To do
Development

No branches or pull requests

3 participants