Convert Green Button API from Swagger 1.2 to OpenAPI 3.0#1
Merged
Conversation
Convert the complete Green Button (ESPI) API definition from Swagger 1.2 to OpenAPI 3.0.0 with comprehensive documentation and examples. Changes: - Converted 11 Swagger 1.2 API declarations to OpenAPI 3.0 paths - Created 16 schema files from XSD definitions (atom.xsd, espi.xsd) - Added 7 reusable parameter components for query parameters - Defined OAuth2 security scheme with authorizationCode and clientCredentials flows - Added 27 path files covering all Green Button API endpoints - Included XML response examples extracted from sample ESPI data - Properly annotated XML namespaces (Atom and ESPI) - Updated .gitignore to exclude .idea and .claude directories - Configured Redocly to handle XML examples for application/atom+xml Resources converted: - ApplicationInformation, Authorization, Batch - UsagePoint, MeterReading, ReadingType, IntervalBlock - LocalTimeParameters, ElectricPowerQualitySummary, UsageSummary - ServiceStatus Validation: Passes npx @redocly/cli lint with zero errors and warnings Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
…and deployment Add automated CI/CD pipeline that validates OpenAPI specifications and deploys documentation to GitHub Pages. Features: - Runs on all pull requests and pushes to main - Validates OpenAPI spec with Redocly lint - Builds and bundles the specification - Uploads bundled spec as artifact (30-day retention) - Deploys documentation to GitHub Pages on main branch - Includes comprehensive workflow documentation Validation checks: - OpenAPI spec validation - Linting rules enforcement - Build verification Documentation deployment: - Automatic deployment to GitHub Pages on main branch pushes - Clean artifact management - Proper permissions and concurrency controls Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The build script was missing the input file path, causing CI/CD to fail. Updated to explicitly bundle openapi/openapi.yaml. Fixes CI/CD validation error: 'At least one inline API must be specified when using --output.' Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
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.
Summary
This PR converts the complete Green Button (ESPI) API definition from Swagger 1.2 to OpenAPI 3.0.0 with comprehensive documentation, examples, and automated CI/CD.
What's Changed
🔄 API Conversion
📚 Documentation & Examples
🤖 CI/CD Pipeline
🛠️ Configuration
Resources Converted
Validation
✅ Passes all checks:
npx @redocly/cli lintreturns zero errors and zero warningsFiles Changed
Breaking Changes
Next Steps After Merge
Testing
Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com