Feature/expose configuration error #3205
Draft
+344
−54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Expose ConfigurationError for Service Configuration Conflicts in SwarmKit
- What I did
Added a
ConfigurationErrorfield to the SwarmKitServiceAPI to expose configuration conflicts (e.g., duplicate service names or conflicting port bindings) instead of silently dropping services. This proof-of-concept improves operator visibility and fosters discussion on error handling.- How I did it
manager/allocator/allocator.goto detect port conflicts and setConfigurationErrorwithStatus.StateasDISABLED.manager/dispatcher/dispatcher.goto check for duplicate service names during updates, settingConfigurationErrorif conflicts occur.manager/state/store.gopersistsConfigurationErrorand validates disabled status.