# AWX API Golang Client **URL:** \ **Category:** AWX Project\ **Tags:** awx, kubernetes\ **Created:** [April 8, 2018, 2:18pm UTC](https://forum.ansible.com/t/awx-api-golang-client/27218 "2018-04-08T14:18:59Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mtayer](https://avatars.discourse-cdn.com/v4/letter/m/a88e57/32.png) [@mtayer](https://forum.ansible.com/u/mtayer)\ **Post date:** [April 8, 2018, 2:18pm UTC](https://forum.ansible.com/t/awx-api-golang-client/27218/1 "2018-04-08T14:18:59Z")
Hello, As part of efforts to develop an internal Openshift autoheal component, and because we could not find an official or otherwise maintained golang client for the AWX API we created a new one. It is currently embedded in that project[1] but we are interested in donating it and resuming development for it under the Ansible project umbrella. I’m writing here to ask if you would be willing to accept the new project, and if there are guidelines or specific requirements for including our client under the Ansible org. I’ve gained experience in a similar effort maintaining the most widely used ruby client for Kubernetes[2]. I think the Ansible org is the best place for growing the client and I think the community would gain from it as well. Thanks, Mooli [1] [https://github.com/openshift/autoheal/tree/master/pkg/awx](https://github.com/openshift/autoheal/tree/master/pkg/awx) [2] [https://github.com/abonas/kubeclient](https://github.com/abonas/kubeclient) ---
**Author:** ![mtayer](https://avatars.discourse-cdn.com/v4/letter/m/a88e57/32.png) [@mtayer](https://forum.ansible.com/u/mtayer)\ **Post date:** [April 10, 2018, 9:46am UTC](https://forum.ansible.com/t/awx-api-golang-client/27218/2 "2018-04-10T09:46:48Z")
bump ---
**Author:** ![Bill\_Nottingham1](https://avatars.discourse-cdn.com/v4/letter/b/58f4c7/32.png) [@Bill\_Nottingham1](https://forum.ansible.com/u/Bill_Nottingham1)\ **Post date:** [April 10, 2018, 3:19pm UTC](https://forum.ansible.com/t/awx-api-golang-client/27218/3 "2018-04-10T15:19:10Z")
mtayer@redhat.com (mtayer@redhat.com) said: > As part of efforts to develop an internal Openshift autoheal component, and > because we could not find an official or otherwise maintained golang client > for the AWX API we created a new one. > > It is currently embedded in that project[1] but we are interested in > donating it and resuming development for it under the Ansible project > umbrella. > > I'm writing here to ask if you would be willing to accept the new project, > and if there are guidelines or specific requirements for including our > client under the Ansible org. > > I've gained experience in a similar effort maintaining the most widely used > ruby client for Kubernetes[2]. I think the Ansible org is the best place > for growing the client and I think the community would gain from it as well. Ideally, this sort of thing would have docs & tests, so it could be run through the same sorts of CI as the rest of AWX. That way we could know when the bindings might break, or when they might need updated for new features. Bill ---
**Author:** ![mtayer](https://avatars.discourse-cdn.com/v4/letter/m/a88e57/32.png) [@mtayer](https://forum.ansible.com/u/mtayer)\ **Post date:** [April 11, 2018, 2:19pm UTC](https://forum.ansible.com/t/awx-api-golang-client/27218/4 "2018-04-11T14:19:16Z")
> [mtayer@redhat.com](mailto:mtayer@redhat.com) ([mtayer@redhat.com](mailto:mtayer@redhat.com)) said: > > > As part of efforts to develop an internal Openshift autoheal component, and > > because we could not find an official or otherwise maintained golang client > > for the AWX API we created a new one. > > > > It is currently embedded in that project[1] but we are interested in > > donating it and resuming development for it under the Ansible project > > umbrella. > > > > I’m writing here to ask if you would be willing to accept the new project, > > and if there are guidelines or specific requirements for including our > > client under the Ansible org. > > > > I’ve gained experience in a similar effort maintaining the most widely used > > ruby client for Kubernetes[2]. I think the Ansible org is the best place > > for growing the client and I think the community would gain from it as well. > > Ideally, this sort of thing would have docs & tests, so it could be run > through the same sorts of CI as the rest of AWX. That way we could know > when the bindings might break, or when they might need updated for new > features. > > Bill Thanks, I’m extracting the client to a separate repository and adding documentation and tests. I understood from your response that the tests should run against an actual, latest, AWX server started in the test environment, is that the general direction?