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

S3 integration component is always loaded #644

Open
ss89 opened this issue Dec 18, 2021 · 0 comments · May be fixed by #645
Open

S3 integration component is always loaded #644

ss89 opened this issue Dec 18, 2021 · 0 comments · May be fixed by #645

Comments

@ss89
Copy link
Contributor

ss89 commented Dec 18, 2021

When i write an integration test component the s3 component is always loaded even though my config that is used does not have any cloud configuration.

This seems to come from the relatively new PostProcessor UseLocalstackDefaultsConfigPostProcessor.

It is adding the cloud.aws.s3 config keys because of the init func of the pkg/cloud/aws/s3/client.go, which is executed due to the fixture loaders all lying in the same directory.

So as soon as one fixture loader is used, the setting is set and a minio container will be started, even if not needed.

@ss89 ss89 linked a pull request Dec 18, 2021 that will close this issue
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 a pull request may close this issue.

1 participant