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 Spin SQS Trigger expects the following AWS configuration variables to be set in the environment at start up:
AWS_DEFAULT_REGION
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_SESSION_TOKEN
We could support configuring these by updating the SpinApp CRD to contain an sqs section:
sqs
spec: createDeployment: true deploymentConfig: runtimeClassName: wasmtime-spin-v2 sqs: - aws_default_region: us-west-2 - aws_secret_access_key: valueFrom: secretKeyRef: name: "my-super-secret" key: "turso-token"
Alternatively, the trigger could be updated to get these values from runtime config instead: fermyon/spin-trigger-sqs#52
The text was updated successfully, but these errors were encountered:
Alternatively: spinkube/skips#9
Sorry, something went wrong.
No branches or pull requests
The Spin SQS Trigger expects the following AWS configuration variables to be set in the environment at start up:
AWS_DEFAULT_REGION
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_SESSION_TOKEN
We could support configuring these by updating the SpinApp CRD to contain an
sqs
section:Alternatively, the trigger could be updated to get these values from runtime config instead: fermyon/spin-trigger-sqs#52
The text was updated successfully, but these errors were encountered: