Skip to content

Report the correct version and revision for Geo node status requests

What does this MR do?

Ensures that when requesting Geo node status details, the correct version and revision is reported

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

At present, we report the current node's version and revision for all nodes.

Screenshots (if relevant)

Screenshot_from_2018-02-01_20-01-22

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • API support added
  • Tests added for this feature/bug
  • Review
    • Has been reviewed by Backend
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together
  • Internationalization required/considered
  • If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
  • End-to-end tests pass (package-qa manual pipeline job)

What are the relevant issue numbers?

Closes #4782 (closed)

Edited by Nick Thomas

Merge request reports