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

Datasource with allowCrossNameSpaceImport get cm/secret in ns with grafana #1861

Open
sentoz opened this issue Feb 13, 2025 · 1 comment
Open
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sentoz
Copy link
Contributor

sentoz commented Feb 13, 2025

Is your feature request related to a problem? Please describe.
Store a datasource covered with variables in one namespace, and in each other namespace have its own grafana and cm/sercet with a set of variables to configure the data source.

Describe the solution you'd like
So that when using a datasource with allovCrossNatesSpaceImport, it would be possible to use the values ​​of variables from cm/secret located in ns with grafana, and not just in ns with the datasource itself

@sentoz sentoz added enhancement New feature or request needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 13, 2025
@sentoz sentoz changed the title Datasource with allovCrossNatesSpaceImport get kam/secret in ns with grafana Datasource with allovCrossNatesSpaceImport get cm/secret in ns with grafana Feb 13, 2025
@theSuess theSuess changed the title Datasource with allovCrossNatesSpaceImport get cm/secret in ns with grafana Datasource with allowCrossNameSpaceImport get cm/secret in ns with grafana Feb 17, 2025
@theSuess theSuess added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 17, 2025
@theSuess
Copy link
Member

Thanks for the feature request.

We discussed this in our weekly sync call and are not against this feature, but have concerns around maintainability.

If you could provide a Proof-of-Concept for this as a PR, we are open to discussing this further but don't want to spend too many resources on this right now.

@theSuess theSuess removed the enhancement New feature or request label Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants