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.

Sign up for GitHub

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

Jump to bottom

Enceladus and Menas model compatibility #37

Open
GeorgiChochov opened this issue Dec 2, 2018 · 0 comments
Open

Enceladus and Menas model compatibility #37

GeorgiChochov opened this issue Dec 2, 2018 · 0 comments
Labels
Conformance Conformance Job affected feature New feature Menas Menas component affected priority: low Nice to have Standardization Standardization Job affected

Comments

@GeorgiChochov
Copy link
Collaborator

Currently we have no way of ensuring that the models used in Enceladus (std and conformance) are compatible versions with the ones stored in Menas. We can add a header to the HTTP requests that says what model version Enceladus is using, then Menas can check compatibility and respond accordingly.

If the header is not specified Menas should ignore the compatibility check to avoid breaking compatibility for people using Encealdus as a library.
@GeorgiChochov GeorgiChochov added feature New feature Menas Menas component affected Conformance Conformance Job affected labels Dec 2, 2018
@GeorgiChochov GeorgiChochov added the Standardization Standardization Job affected label Jan 23, 2019
@GeorgiChochov GeorgiChochov added this to the Enceladus v1.0 milestone Mar 12, 2019
@GeorgiChochov GeorgiChochov added the priority: low Nice to have label Jul 12, 2019
@GeorgiChochov GeorgiChochov removed this from the Enceladus v1.0 milestone Aug 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Conformance Conformance Job affected feature New feature Menas Menas component affected priority: low Nice to have Standardization Standardization Job affected
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GeorgiChochov