Adding v1beta1 - #6

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

@googlebot I signed it!

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

Looks reasonable to me - I don't know what the status of these client libraries are though.

Thanks for sending these in though :D Have you tested this and is it working? My leaning is to just merge this and we can normalize the client library situation later.

Looks reasonable to me - I don't know what the status of these client libraries are though.

Me neither! I noticed there is no grafeas.swagger.json in the latest grafeas release too... These were generated on the assumption the swagger is accurate but I see a few issues suggesting they might not be. I will test today and let you know the outcome.

Related - grafeas/grafeas#95

Last I checked, the protoc tool wasn't able to generate a correct Swagger spec from the protos because the OpenAPI spec isn't rich enough to support the HTTP mappings we use in the protos (https://cloud.google.com/apis/design/standard_methods). @aysylu on the status of this.

@danielwhatmuff are you using this Python client library for v1beta1? If you are, and you need it, I'm happy to merge this generated library works for you in its current state.

I was trying to get it working yes but am getting 404s when making calls to the docker image grafeas/grafeas:0.1.0 running locally.

Is there an alternative image tag I should test against?

@vtsao @aysylu what are your thoughts on this?

@danielwhatmuff: you'll want to use v0.1.0 tag: docker pull us.gcr.io/grafeas/grafeas-server:v0.1.0. Does it work with this tag?

@danielwhatmuff: we've moved to using semantic versioning for the server and client lib releases, see versioning doc and client-go. Could you please re-generate this to be 0.1.0 version? Thank you!

Sure, I will try with the 0.1.0 version.

@danielwhatmuff: thanks!

Closing this due to no activity since Sep 2019. Happy to review another PR for the 0.1.0 version of the client.