Best Practice for handling potential server errors with Declarative Management

Hello All,

I come to ask a question that I haven't been able to find the docs. I continue to work on implementing declarative management and while working there is a question/concern I have.

I have noticed that during some destructive testing, if the device is attempting to fetch a configuration and the server responds with a 503 (or any server related error) then the device will wipe all configurations and attempt to reapply them.

Is there any way to prevent this by intercepting status codes or would the only real solution be to force down a temp/test config if the real config can't be fetched from the server?

Answered by Device Management Engineer in 871915022

Please file a feedback report with a sysdiagnose from a device that experienced this problem.

Please file a feedback report with a sysdiagnose from a device that experienced this problem.

Details to file the bug:

Bug Reporting: How and Why? has tips on creating your bug report.

Albert Pascual
  Worldwide Developer Relations.

Best Practice for handling potential server errors with Declarative Management
 
 
Q