You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
87
91
@@ -929,3 +933,32 @@ A powerful feature of Conductor is the ability to version workflows. You should
929
933
930
934
* Versioning allows safely testing changes by doing canary testing in production or A/B testing across multiple versions before rolling out.
931
935
* A version can also be deleted, effectively allowing for "rollback" if required.
936
+
937
+
938
+
## Development
939
+
940
+
### Client Regeneration
941
+
942
+
When updating to a new Orkes version, you may need to regenerate the client code to support new APIs and features. The SDK provides comprehensive guides for regenerating both sync and async clients:
943
+
944
+
#### Sync Client Regeneration
945
+
946
+
For the synchronous client (`conductor.client`), see the [Client Regeneration Guide](src/conductor/client/CLIENT_REGENERATION_GUIDE.md) which covers:
947
+
948
+
- Creating swagger.json files for new Orkes versions
949
+
- Generating client code using Swagger Codegen
950
+
- Replacing models and API clients in the codegen folder
951
+
- Creating adapters and updating the proxy package
952
+
- Running backward compatibility, serialization, and integration tests
953
+
954
+
#### Async Client Regeneration
955
+
956
+
For the asynchronous client (`conductor.asyncio_client`), see the [Async Client Regeneration Guide](src/conductor/asyncio_client/ASYNC_CLIENT_REGENERATION_GUIDE.md) which covers:
957
+
958
+
- Creating swagger.json files for new Orkes versions
959
+
- Generating async client code using OpenAPI Generator
960
+
- Replacing models and API clients in the http folder
961
+
- Creating adapters for backward compatibility
962
+
- Running async-specific tests and handling breaking changes
963
+
964
+
Both guides include detailed troubleshooting sections, best practices, and step-by-step instructions to ensure a smooth regeneration process while maintaining backward compatibility.
0 commit comments