You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
ss89
linked a pull request
Dec 18, 2021
that will
close
this issue
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.
The text was updated successfully, but these errors were encountered: