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
Describe what should be investigated or refactored
The init package is currently able to be configured with Zarf variables to support an S3 backend. See github.com/defenseunicorns/narwhal-delivery-iac-swf-reference-deployment for an example of a configuration with an s3 backend. There are no tests in this repo to ensure that this S3 backend works, so certain changes to the registry portion of the init package cannot be made with confidence.
This is the case for PR #3241 which solves a legitimate bug within the init package, but we need a test to know if this change breaks the s3 backed init package variant
The text was updated successfully, but these errors were encountered:
A good option to implement a test for S3 integration would be to use a S3 compatible local store. This https://github.com/seaweedfs/seaweedfs is one option of what we could use. We should do some research if there is a S3 in memory implementation in Go to make the integration with the e2e tests easier.
Describe what should be investigated or refactored
The init package is currently able to be configured with Zarf variables to support an S3 backend. See github.com/defenseunicorns/narwhal-delivery-iac-swf-reference-deployment for an example of a configuration with an s3 backend. There are no tests in this repo to ensure that this S3 backend works, so certain changes to the registry portion of the init package cannot be made with confidence.
This is the case for PR #3241 which solves a legitimate bug within the init package, but we need a test to know if this change breaks the s3 backed init package variant
The text was updated successfully, but these errors were encountered: