WIP feat(email): verification reminder email enqueue #1090
Conversation
| queueUrl: { | ||
| doc: 'The verification reminder queue URL to use (should include https://sqs.<region>.amazonaws.com/<account-id>/<queue-name>)', | ||
| format: String, | ||
| env: 'VERIFICATION_REMINDER_QUEUE_URL', |
vladikoff
Oct 28, 2015
Author
Contributor
@dannycoates are queue permissions guarded by QueuePolicy (ref https://github.com/mozilla/fxa-dev/blob/6c922db044531934ed33f09be78222daee9993c5/aws/cloudformation/moz-single.json#L264 ) or something else? How would you test / access the queue locally?
@dannycoates are queue permissions guarded by QueuePolicy (ref https://github.com/mozilla/fxa-dev/blob/6c922db044531934ed33f09be78222daee9993c5/aws/cloudformation/moz-single.json#L264 ) or something else? How would you test / access the queue locally?
dannycoates
Oct 28, 2015
Member
How would you test / access the queue locally?
What do you mean by locally, non-AWS like local-dev?
How would you test / access the queue locally?
What do you mean by locally, non-AWS like local-dev?
vladikoff
Oct 28, 2015
Author
Contributor
First to confirm, I assume it is a Yes to
are queue permissions guarded by QueuePolicy?
Otherwise:
What do you mean by locally, non-AWS like local-dev?
For local dev we were planning to have a local (non-AWS) queue to manage these (for self-hosters and non-AWS deployments as well).
However I wanted to test real SQS locally, would the aws-sdk module look for my AWS creds via process.env?
First to confirm, I assume it is a Yes to
are queue permissions guarded by QueuePolicy?
Otherwise:
What do you mean by locally, non-AWS like local-dev?
For local dev we were planning to have a local (non-AWS) queue to manage these (for self-hosters and non-AWS deployments as well).
However I wanted to test real SQS locally, would the aws-sdk module look for my AWS creds via process.env?
dannycoates
Oct 28, 2015
Member
However I wanted to test real SQS locally, would the aws-sdk module look for my AWS creds via process.env?
I'm not sure thats such a great idea or necessary, unless you're only doing it for now while you're getting started. It complicates the permissions to SQS. I think we should keep it internal network only.
credentials: via credentials file http://aws.amazon.com/sdk-for-node-js/
policy: http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/UsingIAM.html
However I wanted to test real SQS locally, would the aws-sdk module look for my AWS creds via process.env?
I'm not sure thats such a great idea or necessary, unless you're only doing it for now while you're getting started. It complicates the permissions to SQS. I think we should keep it internal network only.
credentials: via credentials file http://aws.amazon.com/sdk-for-node-js/
policy: http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/UsingIAM.html
vladikoff
Oct 28, 2015
Author
Contributor
unless you're only doing it for now while you're getting started.
Yeap that was the plan, thanks Danny!
unless you're only doing it for now while you're getting started.
Yeap that was the plan, thanks Danny!
vladikoff
force-pushed the
sqs-verify-email
branch
2 times, most recently
from
cc105e5
to
8730569
|
closing this, new PR will use DB instead of SQS |
Fixes #1081