Current Behavior
The CLI currently zips the entire spec folder and passes it to the backend without awareness of META file contents. All logic for reading and processing META files happens on the backend.
Desired Behavior
Ability to specify which META files to use via CLI arguments when serving or generating (portal or SDK). This would allow teams to manage multiple META configurations and select the appropriate one for their current workflow.
Use Cases
- Teams managing multiple API configurations (development, staging, production)
- Environment-specific settings that need different META file configurations
- Modular API documentation setups where different META files control different aspects
- Teams that want to switch between different configuration profiles without manual file manipulation
Additional Context
This feature would eliminate the need for teams to manually manipulate META files using sed/grep/awk to remove portions between comment blocks, providing a cleaner and more maintainable approach to managing multiple API configurations.
Current Behavior
The CLI currently zips the entire spec folder and passes it to the backend without awareness of META file contents. All logic for reading and processing META files happens on the backend.
Desired Behavior
Ability to specify which META files to use via CLI arguments when serving or generating (portal or SDK). This would allow teams to manage multiple META configurations and select the appropriate one for their current workflow.
Use Cases
Additional Context
This feature would eliminate the need for teams to manually manipulate META files using sed/grep/awk to remove portions between comment blocks, providing a cleaner and more maintainable approach to managing multiple API configurations.