Open huhouhua opened 9 months ago
Argo CD has a go client (the CLI uses it). Generating other clients as part of our build process would be really great imo. But it is maintenance overhead, so I'd only want to do it in the main repo if the build process was simple and stable.
Argo CD has a go client (the CLI uses it). Generating other clients as part of our build process would be really great imo. But it is maintenance overhead, so I'd only want to do it in the main repo if the build process was simple and stable.
ok, If you are concerned about maintenance, I can maintain these client SDK
Sounds great! If you want to set up a PoC in a personal repo, I'm sure we'd be happy to consider moving it into argoproj-labs, if that's something you'd like to do.
ok
Summary
What change you think needs making.
Provide different programming languages API interface SDK
Motivation
Please give examples of your use case, e.g. when would you use this.
For example, you need to write a Client SDK to call the http API directly now, if provide an API Client SDK for different programming languages, so that more users, do not have to care about the API problem, directly use the SDK, which can simplify their development workload.
Proposal
How do you think this should be implemented? Priority is given to SDKS for major programming languages, but I can be responsible for implementing Client SDKS for Golang, java, C# if needed.