Skip to content

CP-46933: Expose XAPI API version in the output of HTTP API /updates #5886

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

Conversation

gangj
Copy link
Contributor

@gangj gangj commented Jul 29, 2024

XAPI API version is exposed from updateinfo.xml, to expose it in the output of HTTP API /updates, a new json field "xapi-api-version" is added in the json output only when XAPI API version is exposed from updateinfo.xml successfully, otherwise the returned json data keeps the original format.


This change is Reviewable

@gangj
Copy link
Contributor Author

gangj commented Jul 29, 2024

There is a build failure:

File "ocaml/gencert/selfcert.ml", line 46, characters 43-45:
46 | let () = Mirage_crypto_rng_unix.initialize ()
                                                ^^
Error: This expression has type unit but an expression was expected of type
         'a Mirage_crypto_rng.generator
       Mirage_crypto_rng.generator is abstract because no corresponding cmi file was found in path.
make: *** [Makefile:16: build] Error 1
Error: Process completed with exit code 2.

@gangj gangj marked this pull request as draft July 29, 2024 02:58
Copy link
Contributor Author

@gangj gangj left a comment

Choose a reason for hiding this comment

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

Reviewable status: 0 of 4 files reviewed, 1 unresolved discussion

a discussion (no related file):
Enable reviewable


@gangj gangj force-pushed the private/gangj/CP-46933 branch from 6aaaec0 to b9f8c0c Compare July 30, 2024 02:21
@gangj gangj marked this pull request as ready for review July 30, 2024 03:53
@gangj gangj changed the title CP-49378: Expose XAPI API version in the output of HTTP API /updates CP-46933: Expose XAPI API version in the output of HTTP API /updates Jul 31, 2024
@gangj gangj force-pushed the private/gangj/CP-46933 branch from b9f8c0c to 5953bb4 Compare July 31, 2024 08:44
@gangj gangj force-pushed the private/gangj/CP-46933 branch 2 times, most recently from 6a367e2 to e3e605b Compare August 6, 2024 07:49
XAPI API version is exposed from updateinfo.xml, to expose it in the
output of HTTP API /updates, a new json field "xapi-api-version" is added
in the json output only when XAPI API version is exposed from
updateinfo.xml successfully, otherwise the returned json data keeps the
original format.

Signed-off-by: Gang Ji <gang.ji@citrix.com>
@gangj gangj force-pushed the private/gangj/CP-46933 branch from e3e605b to c5918fa Compare August 6, 2024 08:09
@gangj gangj merged commit 784ddee into xapi-project:feature/update-backwards-compat Aug 8, 2024
15 checks passed
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.

3 participants