docs: add AWS SQS source to README

[srvaroa]

No description provided.

[knative-prow-robot]

Hi @srvaroa. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vaikas]

Might want to clarify that the Receive Adapter runs as this account. So, the effect is that we access the secret as this Service Account, but it's because the Receive Adapter runs as this Service Account.

Maybe add something like this (not verbatim, but shrug)

// serviceAccountName is the name of the ServiceAccount that will be used to
// run the Receive Adapter Deployment.

[evankanderson]

This seems to parallel line 184 for the GcpPubSubSource.

[evankanderson]

/lgtm
/approve

Now that we have https://github.com/knative/docs/tree/master/eventing/sources, we might want to consider replacing this list with a reference to that doc.

That might also require extracting some additional parameter information about the sources, which would be interesting to see if we can automate.

For now, I'm fine with adding this here, but I expect the other page to become the canonical one.

[evankanderson]

This seems to parallel line 184 for the GcpPubSubSource.

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: evankanderson, srvaroa

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [evankanderson]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vaikas]

@evankanderson re: automating the parameter information, I've been playing with using the OpenAPI validation that's part of the CRDs with both Google Cloud Scheduler / Google Cloud Storage, and I think it's pretty good start.