Hey Team, I would like to be able to version modules independently of each other. Currently it seems I can only version everything.
Currently, Apidog’s version control is more based on all modules. If you need independent version management for specific modules, you can try creating separate branches for each module and maintain changes only within those branches. If this doesn’t meet your needs, feel free to share how you’d like to manage module versions, and we can explore further optimizations.
As each module is a different service, their endpoints may change independently of each other. When we wish to publish a new version through the docs then the only way I have currently is to version everything.
I am working towards one project and multiple modules as a way to produce docs for these different services. So now I can’t version those independently and I have to have either separate projects and separate docs or modules with no versioning.
Got it! I’ll forward this feedback to our product manager to explore optimization options for independent module versioning.
I have the same query
Is your expected outcome the same? Let me know and I’ll forward it to the product team.
we have microservices based architecture. It is possible that one service exceeds some other service in versions. It would be great to have the API grow independently from other modules (services).
Understood. We’ll consider how to optimize this feature.
We are facing the same issue. Currently we are working with different projects for each microservice but this prohibits sharing common schemas, variables, etc. So a module based versioning would be great as we could merge all microservices into 1 project
Thank you for your feedback. We’ll consider how to optimize this feature.