Identify differences to latest OSBAPI 2.17 spec and document missing features#484
Draft
Identify differences to latest OSBAPI 2.17 spec and document missing features#484
Conversation
Co-authored-by: eruvanos <9437863+eruvanos@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Identify differences to latest spec version
Identify differences to latest OSBAPI 2.17 spec and document missing features
Sep 28, 2025
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.
This PR addresses issue #X by providing a comprehensive analysis of the gaps between the current openbrokerapi implementation (supporting OSBAPI 2.13+) and the latest Open Service Broker API 2.17 specification.
Analysis Summary
The current implementation supports OSBAPI 2.13+ as the minimum version but is missing several key features introduced in 2.17. This analysis identifies 13 major feature categories that are not yet implemented:
Critical Missing Features
Service Binding Rotation - A major new capability in 2.17 that allows credentials to be rotated seamlessly:
ServicePlan.binding_rotatablefield to declare rotation supportBindDetails.predecessor_binding_idfor creating successor bindingsBindingMetadatawith expiration timing (expires_at,renew_before)Maintenance Info Object - Comprehensive maintenance operation support:
MaintenanceInfoclass with version and descriptionMaintenanceInfoConflicterror code for version mismatchesService Instance Metadata - Enhanced metadata support:
ServiceInstanceMetadatawith labels and attributesNetwork Endpoints - Service connectivity information:
Endpointclass defining host, ports, and protocolAdditional Enhancements
Service.allow_context_updatesfor context change supportServicePlan.maximum_polling_durationfor per-plan polling limitsFiles Added
OSBAPI_2_17_ANALYSIS.md- Detailed technical analysis with implementation requirementsMISSING_FEATURES_SNIPPETS.md- Ready-to-use code snippets for implementing each missing featureTODO.md- Cross-referenced existing TODO items with new findingsImplementation Notes
All identified missing features are backwards compatible additions that can be implemented incrementally without breaking existing broker implementations. The analysis provides exact code locations and implementation patterns to facilitate future development.
This work establishes a clear roadmap for bringing the library up to full OSBAPI 2.17 compliance while maintaining compatibility with existing 2.13+ brokers.
Original prompt
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.