You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix drift and update failures for adopted edge transport nodes
node_id-adoption ConflictsWith advanced_configuration, credentials,
form_factor and management_interface, so config for an adopted node
never sets them. Read still populated all of them unconditionally
from the API, showing permanent spurious drift on every plan;
form_factor additionally carries a static schema Default that would
keep re-asserting itself even with Read fixed, so it needs a
DiffSuppressFunc instead.
More seriously, Update always rebuilt the request body from config
via policyEdgeTransportNodePatch, same as a freshly created node. For
an adopted node that sends an empty management_interface, which NSX
rejects as missing required fields on any update - including one
only triggered by the spurious drift above. Route Update through the
same GET-then-merge policyEdgeTransportNodePredeployedPatch that
Create already uses for adoption.
0 commit comments