-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
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
feat: ucan stream handles receipts #174
Conversation
View stack outputs
|
45543c0
to
e7bf749
Compare
@@ -189,8 +189,17 @@ export function UcanInvocationStack({ stack, app }) { | |||
deadLetterQueue: spaceMetricsDLQ.cdk.queue, | |||
}) | |||
|
|||
// TODO: keep for historical content that we might want to process |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WORKFLOW: 'application/invocations+car', | ||
RECEIPT: 'application/receipt+dag-cbor' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- the + suffix denotes an existing media type which are registered as
vnd.ipld.car
andvnd.ipld.dag-cbor
- the prefix is a tree, and we can add things to the vnd tree without much fuss like:
application/vnd.w3.ucan+vnd.ipld.car
application/vnd.w3.ucan.receipt+vnd.ipld.dag-cbor
of if we really don't care then
application/x.ucan+vnd.ipld.car
application/x.ucan.receipt+vnd.ipld.dag-cbor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note that our notion of an invocation is currently a short lived ucan delegation that we as a service provider choose to interpret as an invocation. they are not explicitly invocation ucans.
This PR hooks kinesis consumers with receipts, instead of previous world where it would hook up with workflows. For this, it simply filters out Kinesis events that are not receipts as they should not be account for the metrics we want to track at the moment.
As talked in today`s morning sync, setting up a new Kinesis stream so that: