Description
Feature Request
Background:
Today the frontend o11y resources need to be scoped to a cloud provider rather than stack provider. Other resources like k6 and synthetics work around this by having an install resource which configures/returns whatever we need the cloud provider for and then use a stack based resource to create the underlying resources. For frontend o11y this would be the frontend o11y app.
Request:
Please can we create an "installation" resource for frontend o11y which configures whatever the frontend o11y app resources needs today and then use a stack based resource to actually create the app.
Why
This is useful for separation of concerns. The Grafana cloud scoped provider creates the stack, creates access policies, installs plugins, etc. The stack scoped provider then uses the stack and configures the stack - in this scenario, it creates the frontend o11y app
Extra context:
The whole concept of requiring an install resource or a resource that needs more than just a stack scoped provider isn't a good thing. It adds more friction to usability. The dream state would be the grafana_cloud_stack resource configures all of this OOTB within any extra steps. Given that isn't possible in the scope of this ticket I feel following the same paradigm as the others is better than doing a separate thing