API calls stopped working on Humio Cloud

wknapik commented 4 years ago

Hi,

We're using Humio Cloud v1.11.0. The automation we've had in place for quite a while, for creating views and adding users to them, started failing with errors like:

{"data":null,"errors":[{"message":"Cannot query field 'addMember' on type 'Mutation'. Did you mean 'addUser'? (line 1, column 12):\nmutation { addMember(searchDomainName:\"redacted\", username:\"redacted\",hasDeletionRights:false, hasMembershipAdminRights:false) { clientMutationId } }\n           ^","locations":[{"column":12,"line":1}]}]}

We have not touched this code in a long time, so it seems like a change on the Humio side.

I just started investigating this, so I don't have more information at the moment, but I figured, I'd open this issue in case this is something obvious to you guys. Have there been any backwards-incompatible changes to the API recently ?

Also, I've tried replacing our existing code with calls to humioctl, which would be much more readable/maintainable, but unfortunately, I instantly ran into https://github.com/humio/cli/issues/26 ;/

andejens commented 4 years ago

thank you - we will take a look

JacobJust commented 4 years ago

That api endpoint is replaced with:

mutation {
  updateDefaultGroupMemberships(input: {userName:"user", viewName:"viewname", groups:[Member, Admin, Eliminator]}) {
    groups {
      users {
        username
      }
    }
  }
}

andejens commented 4 years ago

Hi @wknapik - please let us know if it works for you.

wknapik commented 4 years ago

Hi @andejens & @JacobJust,

Yes, this does work, so thanks for the snippet.

The bigger problem here is that an unversioned API is changing in a backwards-incompatible way.

I have a few questions about that:

If the API is going to be versioned in the future
- Will we be notified of a new version becoming available ?
- How many versions will be maintained at any given time ?
- How much time will we have before old versions are no longer supported ? Will we be notified when (or before) they reach EOL ?
if the API is NOT going to be versioned in the future
- Will we be notified of backwards-incompatible changes ahead of time ?
- How much time will we have to adapt ?
- How will we be able to adapt to API changes without versioning ? Will there be a separate API instance with the changes, available at a different url ?

This was unexpected and quite disruptive for us. We'd like to make sure it doesn't happen again.

wknapik commented 4 years ago

Hi @andejens. Any updates on this ?

wknapik commented 4 years ago

Hi @andejens. It's been 3 weeks. Do you have an update ?

andejens commented 4 years ago

Yeah - sorry about that - for now we are not having any active plans for versioning the API, we are evaluating this going forward. My suggestion would be to set up a meeting to discuss this in more detail. I'll reach out to you by mail and coordinate a meeting.

wknapik commented 4 years ago

Hi. Our API calls started failing again today. Have there been more backwards-incompatible changes recently ? View creation is failing.

wknapik commented 4 years ago

Hello ?

wknapik commented 4 years ago

@andejens / @JacobJust ?

wknapik commented 4 years ago

Can we please get an answer ? It's been 6 days now.

wknapik commented 3 years ago

@andejens, @JacobJust it's been 3 weeks, can you please respond ?

humio / issues

API calls stopped working on Humio Cloud #114