[CPREQ-7712] Backward-compatible lightweight enrichment of connections #632
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
InventoryOnlyPatch
s is not preserved on nodes.kubemarine do
runs full enrichment and thus cannot be used before migration.do
#629Solution
kubemarine do
use the new lightweight inventory.globals.nodes.boot.timeout
is moved tonode_defaults.boot.timeout
for the lightweight enrichment to do not depend onglobals
.Breaking changes
globals.nodes.boot.timeout
is moved tonode_defaults.boot.timeout
nodes
,node_defaults
,gateway_nodes
,procedure_history
,values
,cluster_name
sectionsno longer can refer to other sections.
How to apply
Run
kubemarine migrate_kubemarine --force-apply boot_timeout_per_node
Test Cases
TestCase 1
Steps:
globals.nodes.boot.timeout
property.kubemarine migrate_kubemarine --force-apply boot_timeout_per_node
ER:
node_defaults.boot.timeout
TestCase 2
Steps:
kubemarine do
using inventory of very old, no longer supported format.Checklist
Unit tests
test_do.py, test_run_actions.py, test_cluster.py - cover new functionality.