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

Use feature gate for S3 storage #597

Merged
merged 1 commit into from
Jul 3, 2024
Merged

Conversation

AndiDog
Copy link

@AndiDog AndiDog commented Jul 2, 2024

Towards giantswarm/roadmap#3442

To be merged after #596 (stacked PR).

This adds the suggested changes as requested in the review of #593.

@AndiDog AndiDog requested a review from a team July 2, 2024 10:12
@AndiDog AndiDog force-pushed the s3-storage-feature-gate branch from f95969c to 8f61242 Compare July 2, 2024 10:12
@AndiDog AndiDog changed the title Use feature gate Use feature gate for S3 storage Jul 2, 2024
@AndiDog AndiDog force-pushed the s3-storage-feature-gate branch from 8f61242 to 2d92ff0 Compare July 2, 2024 10:30
// yet by the lifecycle policy
for {
log.Info("Listing S3 objects of machine pools")
if feature.Gates.Enabled(feature.MachinePool) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I only found usages of the feature package in the controllers package, or in the main file. It looks like we are introducing a new dependency between this package and the feature package. I'm not sure if this will get accepted upstream, as it seems it goes in a different design direction. I don't know an alternative approach though.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this code runs in the same process, I think it should work functionality-wise. Regarding upstream, that's the risk we take when implementing in the fork first, so we probably need to accept it this time.

@AndiDog AndiDog merged commit 4f0c8f6 into s3-test-fixes Jul 3, 2024
4 of 6 checks passed
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 this pull request may close these issues.

3 participants