Added cloudevents sample using rust sdk

[slinkydeveloper]

Signed-off-by: Francesco Guardiani francescoguard@gmail.com

Proposed Changes

• Adds an example using cloudevents rust sdk to receive events

[slinkydeveloper]

/hold I still need to release the sdk 😄

[slinkydeveloper]

/assign @mattmoor

[mattmoor]

Nice!

[mattmoor]

Can we do this in a multi-stage Dockerfile as the others?

[slinkydeveloper]

I would prefer to avoid it here, it's quite complex and rust users don't always prefer this approach since they basically lose all the local compilation caching

[evankanderson]

I thought clearing the local compilation caching was sort of the point -- any local compiler hijinks would be ironed out and the result would be reproducible by building in Docker.

I'd also expect that Rustaceans who were familiar with both Rust and containers would probably write their own Dockerfile based on the reference, anyway.

[slinkydeveloper]

Compilation caches in rust in theory are reproducible because they're per exact crate versions. What usually matters to rust users is that you don't want to clean the compilation cache, 10 mins every time for building an image is not nice 😄 Experienced rust devs usually have a remote hosted compilation cache, like this one https://github.com/mozilla/sccache, that then they use in their docker file builds

I'd also expect that Rustaceans who were familiar with both Rust and containers would probably write their own Dockerfile based on the reference, anyway.

I think so, they just need to create a multi stage build starting from debian rust image

[slinkydeveloper]

@mattmoor any idea why the it test fails?

[mattmoor]

re: tests, a lot have been failing today because (IIUC) a quay outage. Let's see if it's over.

/retest

[mattmoor]

Need to update: https://github.com/knative/docs/blob/master/docs/serving/samples/README.md

[slinkydeveloper]

/hold cancel

Now we can get this one in

[slinkydeveloper]

@mattmoor ping

[evankanderson]

Taking a look -- a couple small questions, mostly about whether this is targeted at experienced Rust + container developers, or those who might be new to one or both tools.

[evankanderson]

I thought clearing the local compilation caching was sort of the point -- any local compiler hijinks would be ironed out and the result would be reproducible by building in Docker.

I'd also expect that Rustaceans who were familiar with both Rust and containers would probably write their own Dockerfile based on the reference, anyway.

[googlebot]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[evankanderson]

/lgtm
/approve

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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