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

Suggestion: global tags that are applied to dashboards and other resources #404

Open
tiedotguy opened this issue Dec 16, 2022 · 1 comment

Comments

@tiedotguy
Copy link

It would be useful to be able to have a global set of tags which are applied to all supported resources. As a practical example, the ability to define a source repository, so the source of a dashboard can be located.

These would be provided in a provider argument, such as dashboard_tags and detector_tags.

The primary advantage is that users don't need to remember to update every resource individually (and in some cases they may not even be able to update them, such as in a module they only have read-only access to)

This might look something like:

provider "signalfx" {
  version = "..."
  auth_token = "..."
  dashboard_tags = [
    "repo:https://example.com/team/repo",
    "team:awesome",
    "service:example"
  ]
}

All the tags would then be appended on to the resource tags. This might be a map rather than a list, I'm not 100% familiar with how resource tags are used in SignalFx.

@navtej-splunk
Copy link

Hi @tiedotguy,
Thanks a lot for bringing this up. I am PM and would be taking care of this issue.
We appreciate the practicality of defining a source repository for locating dashboard sources. We will consider adding provider arguments like "dashboard_tags" and "detector_tags" to help streamline the tag management process.
Your feedback is valuable, and we will further evaluate this feature. Feel free to share any additional insights or use cases. Thank you.

Best,
Navtej

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants