Allow finalization without provider config - #584
Conversation
96183ff to
d23f20d
Compare
d23f20d to
9e0689c
Compare
Ideally, the clean up of configuration on the device, done in the |
9e0689c to
42910a2
Compare
a5fa644 to
e094166
Compare
I seems this is actually possible with the models we have. I have updated this PR. Thanks for looking at this. |
e094166 to
5216052
Compare
79c8ce5 to
5628284
Compare
Finalize resources before resolving provider-specific configuration so deletion can complete when the referenced configuration no longer exists. Remove provider configuration from delete requests and pass only the resource identity and context required for cleanup. Providers now remove all owned device paths independently of the previous desired state. Cover paths outside primary resource trees, including spanning-tree settings for aggregate interfaces, ManagementAccess VTY access classes, and LLDP configuration before disabling the feature. Add regression tests for missing provider configuration and the affected NX-OS cleanup paths. Signed-off-by: Pujol <enric.pujol@sap.com>
Signed-off-by: Pujol <enric.pujol@sap.com>
5628284 to
139faba
Compare
Merging this branch changes the coverage (1 decrease, 3 increase)
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
More info in commit message.