We would have separate swagger files for each supported version (17.1, 18.1, 18.2, soon 18.3, then 18.4/19.1 etc). My proposal is to make the PoSh versioned internally. Each Orchestrator release introduces not only new API operations, but also changes like new properties on existing DTO models, and behavior changes.Ĭreating a separate PoSh library for each Orchestrator version would be a nightmare for PoSh users, as they would have to ensure they load the correct DLL for the target Orchestrator version (very errror prone and difficult to troubleshoot), and would also be unmanageable for any environment with multiple Orchestrator versions (eg. If we replace the swagger with 18.3 one, the library will likely have issues with existing 18.2 deployments, and more issues with 18.1 and 17.1. This works correctly with 18.2 Orchestrator, may have issues with 18.1 and 17.1, and will not support new 18.3 features. Right now the library uses the 18.2 Orchestrator API client (generated from the checked in swagger file).
0 Comments
Leave a Reply. |