-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
port settings update as transaction #6001
Conversation
With this PR my testing that surfaced #6000 no longer presents an issue. Baseline configuration
Send a request that will cause an address lot allocation failure.Preivously this would result in deleting the switch port settings and leaving a dangling reference for the specified port.
Try again with an address within the lotThis time the allocation succeeds and we can see the address add operation had the desired result in the follow on
Nudge this a different way by providing a bad address lot name
Everything still fine once we fix the address lot name
|
The |
There is a fair amount of code churn here, but it's mostly just moving things around. I factored the clousures that underpin the port settings create and port settings delete methods out into independent functions. Then, I added a new top-level datastore function that performs a port settings update as a client-side database transaction using the factored-out delete and create functions.