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.

Sign up for GitHub

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

Jump to bottom

Add missing e2e tests for different authentication methods #1069

Open
shorim opened this issue May 13, 2024 · 3 comments
Open

Add missing e2e tests for different authentication methods #1069

shorim opened this issue May 13, 2024 · 3 comments
Labels
area/tests Writing/adding/Refactoring tests or checks kind/missing-test Categorizes issue or PR as related to missing automated tests for scenario.

Comments

@shorim
Copy link
Contributor

shorim commented May 13, 2024 •
edited
Loading

Description

For MetricPipeline and TracePipeline, there are 3 different authentication methods: Mutual TLS, Basic Authentication and Token-Based With Custom Headers as doumented here and here.

For LogPipeline, we have 2 different authentication methods: Mutual TLS and Basic Authentication as documented here.

Currently we have e2e tests for the 3 pipelines only for Mutual TLS authentication. We should also add e2e tests for the other authentication methods.

Reasons

Increase our e2e test coverage.

Criterias

  • An e2e test for authentication using Basic Authentication is added for LogPipeline, MetricPipeline and TracePipeline.
  • An e2e test for authentication using Token-Based With Custom Headers is added for MetricPipeline and TracePipeline.
@shorim shorim added area/tests Writing/adding/Refactoring tests or checks kind/missing-test Categorizes issue or PR as related to missing automated tests for scenario. labels May 13, 2024
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 13, 2024
@github-actions GitHub Actions
Copy link

This issue has been automatically closed due to the lack of recent activity.
/lifecycle rotten

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 21, 2024
@kyma-bot kyma-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 21, 2024
@a-thaler a-thaler removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 22, 2024
@a-thaler a-thaler reopened this Jul 22, 2024
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 21, 2024
@a-thaler a-thaler removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/tests Writing/adding/Refactoring tests or checks kind/missing-test Categorizes issue or PR as related to missing automated tests for scenario.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@a-thaler @shorim @kyma-bot