Keeping your gRPC specifications in sync with your codebase is crucial for maintaining accurate SDKs and documentation. Fern provides several automation options to streamline this process.
Use Fern’s GitHub Action to automatically update SDKs and documentation when your Protocol Buffer files change.
If you’re using local-generation: true in your generators.yml, you must install buf.
Validate, lint, and check for breaking changes in your Protocol Buffer files before generating SDKs.
If you’re using Buf Schema Registry, add a step to publish your schemas:
Optionally create a buf.yaml file to customize buf’s linting rules, breaking change detection, and dependencies:
Configure Fern to automatically pull Protocol Buffer files from various sources:
Integrate Fern into your existing CI/CD pipelines to automatically generate SDKs and documentation.
If you’re using local-generation: true in your generators.yml, you must install buf.
If you’re using local-generation: true in your generators.yml, you must install buf.
Set up scheduled updates to ensure your SDKs stay current:
For servers that can generate their own Protocol Buffer definitions:
Track changes to your Protocol Buffer specifications:
Sync different Protocol Buffer services for different components:
Automatically sync Protocol Buffer definitions from running gRPC services that have server reflection enabled:
This ensures that any changes to your gRPC services are automatically reflected in your SDKs and documentation, maintaining consistency across your entire API ecosystem.