-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Is your feature request related to a problem? Please describe.
Having the nobl9_service only able to be referenced where it is created, limits the flexibility of attaching other SLO's if users separate their Terraform code by environments such as production/staging, etc. This forces an end user to have to create independent Nobl9 services for each environment, instead of having a service that can represent all of the controlled environments. The alternative to this approach is being forced to implement nobl9 Terraform code that might exist outside existing code which forces end users into a chicken/egg problem for their SLI metrics.
Describe the solution you'd like
We would like to have a Data Source for the nobl9_service that allows us to lookup existing nobl9 services so that we can pass that into different Terraform plans.
Additional context
N/A