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
Since we added the SQS stuff to the project, it cannot be deployed as-is before some AWS setup has been done, as described in the README.md file, and an SQS-enabled operator has been installed.
Maybe the default should be deploying the project without the new SQS stuff, and SQS would only be enabled by some option, or maybe we could keep it in another git branch, so that people (like @gememma) that want to deploy the playground fast but don't need the SQS stuff can do that easily.
The text was updated successfully, but these errors were encountered:
It may be most convenient to do this with a brief script with flags to enable/ disable various features - this would also leave room for future features to be added. It could also verify that anything required for the features (as in SQS queue splitting) is installed and provide more helpful errors than using `kubectl apply`
Since we added the SQS stuff to the project, it cannot be deployed as-is before some AWS setup has been done, as described in the README.md file, and an SQS-enabled operator has been installed.
Maybe the default should be deploying the project without the new SQS stuff, and SQS would only be enabled by some option, or maybe we could keep it in another git branch, so that people (like @gememma) that want to deploy the playground fast but don't need the SQS stuff can do that easily.
The text was updated successfully, but these errors were encountered: