Closed djshow832 closed 3 months ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign xhebox for approval. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 48.11%. Comparing base (
ac3a39e
) to head (21f5bb4
). Report is 2 commits behind head on master.:exclamation: Current head 21f5bb4 differs from pull request most recent head cd90a92
Please upload reports for the commit cd90a92 to get more accurate results.
:exclamation: There is a different number of reports uploaded between BASE (ac3a39e) and HEAD (21f5bb4). Click for more details.
HEAD has 1 upload less than BASE
| Flag | BASE (ac3a39e) | HEAD (21f5bb4) | |------|------|------| |unittest|1|0|
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Timeline:
2024-08-13 10:54:15.727570214 +0000 UTC m=+265340.431039855
: :ballot_box_with_check: agreed by xhebox.2024-08-13 11:54:53.634980719 +0000 UTC m=+268978.338450378
: :heavy_multiplication_x::repeat: reset by xhebox.2024-08-16 07:21:39.758975131 +0000 UTC m=+511784.462444778
: :ballot_box_with_check: agreed by xhebox.
What problem does this PR solve?
close #2450
When scale-out a component, the version of the scaled node doesn't respect the version specified in the
component_versions
of the original spec.What is changed and how it works?
When creating the new topology, copy
ComponentVersions
tonewPart
, which is used when deploying new instances. Tests show that the component_versions would be merged correctly when parsing the scale-out topology.Check List
Tests
Follow the steps in the issue and check the version of the scale node.
Code changes
Side effects
Related changes
Release notes: