Skip to content
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

CloudEvents route follow up tasks #903

Open
4 of 5 tasks
thjaeckle opened this issue Dec 1, 2020 · 2 comments
Open
4 of 5 tasks

CloudEvents route follow up tasks #903

thjaeckle opened this issue Dec 1, 2020 · 2 comments

Comments

@thjaeckle
Copy link
Member

thjaeckle commented Dec 1, 2020

After the first part of adding a /cloudevents route done in #889 and PR #895 there are some follow ups:

ctron added a commit to ctron/ditto that referenced this issue Dec 4, 2020
This change allows to make the schema optional and also allows to
configure the data content type.

Signed-off-by: Jens Reimann <jreimann@redhat.com>
ctron added a commit to ctron/ditto that referenced this issue Dec 4, 2020
This change allows to make the schema optional and also allows to
configure the data content type.

Signed-off-by: Jens Reimann <jreimann@redhat.com>
ctron added a commit to ctron/ditto that referenced this issue Dec 4, 2020
This change allows to make the schema optional and also allows to
configure the data content type.

Signed-off-by: Jens Reimann <jreimann@redhat.com>
ctron added a commit to ctron/ditto that referenced this issue Dec 4, 2020
This change allows to make the schema optional and also allows to
configure the data content type.

Signed-off-by: Jens Reimann <jreimann@redhat.com>
@ctron
Copy link
Contributor

ctron commented Dec 4, 2020

I created PR #905 … following up in content-type suffix , optional data schema and additional content type.

ctron added a commit to ctron/ditto that referenced this issue Dec 4, 2020
This change allows to make the schema optional and also allows to
configure the data content type.

Signed-off-by: Jens Reimann <jreimann@redhat.com>
ctron added a commit to ctron/ditto that referenced this issue Dec 8, 2020
This change allows to make the schema optional and also allows to
configure the data content type.

Signed-off-by: Jens Reimann <jreimann@redhat.com>
ctron added a commit to ctron/ditto that referenced this issue Dec 9, 2020
This change allows to make the schema optional and also allows to
configure the data content type.

Signed-off-by: Jens Reimann <jreimann@redhat.com>
ctron added a commit to ctron/ditto that referenced this issue Dec 9, 2020
This change allows to make the schema optional and also allows to
configure the data content type.

Signed-off-by: Jens Reimann <jreimann@redhat.com>
ctron added a commit to ctron/ditto that referenced this issue Dec 9, 2020
This change allows to make the schema optional and also allows to
configure the data content type.

Signed-off-by: Jens Reimann <jreimann@redhat.com>
thjaeckle added a commit that referenced this issue Dec 9, 2020
[#903]: Make schema optional, allow alternate content type
thjaeckle added a commit to bosch-io/ditto that referenced this issue Dec 10, 2020
… API 2

Signed-off-by: Thomas Jaeckle <thomas.jaeckle@bosch.io>
@thjaeckle
Copy link
Member Author

@ctron I added OpenAPI documetation in #911 (wanted to have that in the release and the docs for the release).

thjaeckle added a commit to bosch-io/ditto that referenced this issue Dec 10, 2020
* missing specversion lead to 500 error
* exception texts were improved

Signed-off-by: Thomas Jaeckle <thomas.jaeckle@bosch.io>
thjaeckle added a commit that referenced this issue Dec 10, 2020
[#903] provide OpenAPI documentation for /cloudevents on API 2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants