I see. I believe that all different versions on different endpoints is wrong!
Anyway, at this stage, I would say that I spent enough time to evaluate current go-cd and sadly I decided not to go with go-cd this time. Thanks! On Thursday, June 15, 2017 at 4:10:38 PM UTC+10, Ketan Padegaonkar wrote: > > On Thu, Jun 15, 2017 at 11:38 AM <jon...@audiencerepublic.com > <javascript:>> wrote: > >> Thanks for the real quick reply, Ketan >> >> Changing v2 -> v4 worked for /go/api/agents, but not for /go/api/users >> (the same resource not found error). Am I missing something here? >> > > Every api call uses a different version header, because their change > cycles are different. Please consult the API docs before you use any APIs. > > I would like to suggest to make the message useful - rather than 'resource >> not found', 'unsupported version' or 'resource not found due to unsupported >> version header - currently supported versions - (list of versions)', etc. >> Also, some warning messages to log files? >> > > Can you submit an issue on GitHub? > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
