mengw15 commented on PR #6295: URL: https://github.com/apache/texera/pull/6295#issuecomment-4945413411
One question about the broader #5891 series: is there a single feature flag / profile gating the AWS-specific behavior as a whole? This PR and the follow-ups each add their own opt-in keys (`minio.enabled`, `lakekeeperInit.createBucket` / `flavor` here), and the AWS story is assembled via the values overlay. If a master switch is planned (e.g. `aws.enabled` or a deployment profile), would it make sense to land that as its own small PR first, so the subsequent AWS PRs can hang their conditionals off it and the whole feature stays discoverable and can be toggled atomically? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
