aicam commented on PR #6295: URL: https://github.com/apache/texera/pull/6295#issuecomment-4960274726
> 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? I agree that PRs missed the `feature` flag, I just added to all of them. Regarding the master switch plan, we do not want to set AWS as default. And we do not support AWS officially for 2 main reasons: - We have not finalized our final architecture. One of our deployments is using AWS as pilot project and we are iterating on that. So we want to have the flexibility to change our plan as needed. For example in discussion [#5641](https://github.com/apache/texera/discussions/5641) we changed our design and removed `eksctl` and decided to go with Terraform. - By default, we want to support local deployment as our core architecture because almost all of our deployments are on bare-metal machines. Cloud support is a long term goal which we are pursuing but it is not currently supported. -- 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]
