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

chore: add test files for secure json data in kind #1494

Merged

Conversation

smuda
Copy link
Contributor

@smuda smuda commented Apr 16, 2024

This PR adds test files in kind for verifying the existence of Authorization header with GrafanaDatasources with secureJsonData.

@smuda smuda force-pushed the chore/add-kind-test-files-for-secureJsonData branch from 394fcad to 34a5dd1 Compare April 16, 2024 06:17
@smuda smuda changed the title chore: add test for secure json data chore: add test files for secure json data in kind Apr 16, 2024
@HVBE
Copy link
Collaborator

HVBE commented Apr 16, 2024

Hey @smuda ! Thanks for your contributions recently! we really appreciate it!

One question on this PR though, was the intention to have the secureJsonData test to run as part of the chainsaw e2e tests?

@smuda
Copy link
Contributor Author

smuda commented Apr 16, 2024

No it wasn't. I'm in the process of creating such a test as well but this was just to help in the manual tests of #1488 :-)

@HVBE
Copy link
Collaborator

HVBE commented Apr 16, 2024

No it wasn't. I'm in the process of creating such a test as well but this was just to help in the manual tests of #1488 :-)

Thanks! Just wanted to make sure you didn't miss it by accident, but since this is intentional, that's fine with me 😅

@HVBE HVBE enabled auto-merge (squash) April 16, 2024 09:50
@HVBE HVBE merged commit 2ec05c9 into grafana:master Apr 16, 2024
10 checks passed
@smuda smuda deleted the chore/add-kind-test-files-for-secureJsonData branch April 16, 2024 11:14
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

Successfully merging this pull request may close these issues.

None yet

2 participants