Skip to content

Conversation

@AndrewPasika
Copy link
Contributor

No description provided.

@AndrewPasika AndrewPasika changed the title AGILE-3713: draft design AGILE-3713: Design endpoint listing by filter ID message schemas in 20/EFMP Oct 1, 2021
Copy link
Contributor

@PavelAnikeichyk PavelAnikeichyk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it could be better to use italic text style or some other text style to highlight the type of response message in this sentence:

"Repository MUST publish endpoint list by filter response message using the following NATS subject".

And it could be good to use the same style to highlight request/response types in other places.

0020/README.md Outdated
kaa.v1.replica.{client-service-replica-id}.efmp.ep-list-by-filter-request
```

Endpoint filters request message payload MUST be an [Avro-encoded](https://avro.apache.org/) object with the following schema ([0020-endpoint-list-by-filter-request.avsc](./0020-endpoint-list-by-filter-request.avsc)):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change request message type to "Endpoint list by filter"

0020/README.md Outdated
*Endpoint list by filter response* message MUST be sent by repository in response to an [endpoint list by filter request](#endpoint-list-by-filter-request).
Repository MUST publish endpoint list by filter response message to the subject provided in the NATS `replyTo` field of the request.

Endpoint filters response message payload MUST be an Avro-encoded object with the following schema ([0020-endpoint-list-by-filter-response.avsc](./0020-endpoint-list-by-filter-response.avsc)):
Copy link
Contributor

@PavelAnikeichyk PavelAnikeichyk Oct 1, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change response message type to "Endpoint list by filter"

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

Successfully merging this pull request may close these issues.

2 participants