We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Opta deployment flyte.yaml, contains some unnecessary sections like setting up SQS / SNS, granting Cloudwatch eventss role. These can be found here - https://github.com/flyteorg/flyte/blob/master/opta/aws/flyte.yaml#L14-L39
Ideally the only things user should be expected to configure is
This is all, but the current deployment seems to be more complicated than it needs to be.
No response
The text was updated successfully, but these errors were encountered:
Thanks to Austin Bennett for catching this. We seem to have lingering references to these module outputs in the opta file e.g. https://github.com/flyteorg/flyte/blob/master/opta/aws/flyte.yaml#L115
@evalsocket this file is now broken...
Sorry, something went wrong.
yindia
Successfully merging a pull request may close this issue.
Describe the bug
The Opta deployment flyte.yaml, contains some unnecessary sections like
setting up SQS / SNS, granting Cloudwatch eventss role.
These can be found here - https://github.com/flyteorg/flyte/blob/master/opta/aws/flyte.yaml#L14-L39
Expected behavior
Ideally the only things user should be expected to configure is
This is all, but the current deployment seems to be more complicated than it needs to be.
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: