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

[receiver/sshcheck] Update test config and validate it in tests #24739

Closed
DewaldDeJager opened this issue Jul 31, 2023 · 6 comments
Closed

[receiver/sshcheck] Update test config and validate it in tests #24739

DewaldDeJager opened this issue Jul 31, 2023 · 6 comments

Comments

@DewaldDeJager
Copy link
Contributor

The test config file for the SSH check receiver is currently outdated - It uses keyfile in the config rather than key_file. This needs to be updated and the tests extended to pick up issues like this in future.

See the discussion in a related PR here #24676 (comment)_

@github-actions
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@DewaldDeJager
Copy link
Contributor Author

I'd be happy to work on this

@codeboten
Copy link
Contributor

Thanks @DewaldDeJager!

@nslaughter
Copy link
Contributor

I apologize. I've been absent from notifications, but I'm back. I see the issue. Thank you, @DewaldDeJager. Let me know if you would like assistance or I can handle.

@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Oct 18, 2023
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants