For testing purposes, we'd need the ability to point the AWS CLI to a custome endpoint, e.g. a localstack instance (which mocks all the AWS components the collector uses, including the secretsmanager).
The implementation proposed here uses env variables. If they are not set, nothing extra gets added into the call. If we set them (to a value like --endpoint-url http://localstack:4566), then it will automatically and transparently talk to the mocked AWS.
For testing purposes, we'd need the ability to point the AWS CLI to a custome endpoint, e.g. a localstack instance (which mocks all the AWS components the collector uses, including the secretsmanager).
The implementation proposed here uses env variables. If they are not set, nothing extra gets added into the call. If we set them (to a value like
--endpoint-url http://localstack:4566), then it will automatically and transparently talk to the mocked AWS.