Comments (5)
Your proposal makes a lot of sense to me. The type
field would say what we are doing, and the subject
field would say what we are doing it on/with/for.
I think we might need to provide a clear table in the spec stating for each event type what exactly the subject should be, just for clarity.
from spec.
Your proposal makes a lot of sense to me. The
type
field would say what we are doing, and thesubject
field would say what we are doing it on/with/for.I think we might need to provide a clear table in the spec stating for each event type what exactly the subject should be, just for clarity.
Yeah, that's a great idea.
The setup that I'm forming in my mind is, for each event a few elements will go in the CloudEvents context.
We could consider id and source as general cdevents context, mapped to CloudEvents context.
subject instead would map to a different event field based on the event type i.e. PIpelineRun ID, Environment ID etc..
from spec.
With https://github.com/cdevents/spec/blob/main/spec.md#subject in mind: What would the subject look like in cloud events?
from spec.
With https://github.com/cdevents/spec/blob/main/spec.md#subject in mind: What would the subject look like in cloud events?
Since CloudEvents include the source in the headers, subject should be the ID of the CDEvents subject, which is unique within the source.
from spec.
Adressed by #35
from spec.
Related Issues (20)
- Removed and upgraded predicates for service, removal consideration? HOT 3
- We are missing the version part in some of our event examples
- Consider adding artifact.quarantined
- The 'deleted' predicate is not mentioned in the lineup for artifact events
- Ensure consistency amont camel case vs snake case
- Shall we remove the `Run` part from pipeline, task and run events? HOT 2
- Validate schemas towards the JSON metaschema HOT 1
- Link's schema looks to be missing property field HOT 1
- Links not added for new testcase and ticket events in v0.4.0 HOT 2
- Link's ref path needs an update for all the event schemas HOT 6
- Links not added in spec/examples HOT 3
- Instructions on how to use links(external and embedded) for different SDKs HOT 2
- Replace absolute path by relative path in $ref HOT 1
- remove confusing type `Enum or String` HOT 25
- Links are missing in the custom schema
- Rename the "examples" folder so that it's clear it's for validation purposes
- Improvements on automated release
- Linters are only ran on main HOT 2
- How to integrate custom schemaUri for SDKs HOT 1
- Standardizing `outcome` type and values in doc, schema, and examples HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spec.