vectordotdev / vectordotdev/vector

AWS tests fail when no credentials are present

Open
#1,136 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

domain: ci domain: dev domain: tests provider: aws sink: aws_cloudwatch_logs sink: aws_cloudwatch_metrics sink: aws_kinesis_streams sink: aws_s3 sink: elasticsearch
Dominant language
Rust
Stars
22.6k
Forks
2.3k
Avg merge
1d 7h
Merged PRs (30d)
146

Description

Most of our AWS tests that use the DefaultCredentialProvider from rusoto will panic and fail the tests if no form of credentials is present. This can be an issue for running tests on a new VM that might not have any form of AWS creds.

This can be reproduced by creating a VM without aws creds and running the entire test suite.

Some ideas would be to create our own provider that can have a special test mode to inject credentials.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure on a VM without AWS credentials by running the entire test suite, then inspect the AWS tests that use rusoto's DefaultCredentialProvider. Done means the AWS tests no longer panic or fail when no credentials are present, while still exercising their intended behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, rust
Domain
cloud, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.