Bump to aws-sdk-go@v1.12.34

[atsushi-ishibashi]

govendor fetch github.com/aws/aws-sdk-go/....@v1.12.34 didn't fetch new files😕
So additionally I ran the below commands

govendor fetch github.com/aws/aws-sdk-go/service/mediastore@v1.12.34
govendor fetch github.com/aws/aws-sdk-go/service/medialive@v1.12.34
govendor fetch github.com/aws/aws-sdk-go/service/mediaconvert@v1.12.34
govendor fetch github.com/aws/aws-sdk-go/service/mediapackage@v1.12.34
govendor fetch github.com/aws/aws-sdk-go/service/mediastoredata@v1.12.34

[Ninir]

@radeksimko shouldn't this be closed since the merge of #2465?

@atsushi-ishibashi also, the commands you additionally ran are expected: you want to include new services that were not yet registered in the vendor.json file.

The below would only update the vendor.json file for the Go SDK using tag 1.12.34 (but will not fetch any new service added since then):

govendor fetch github.com/aws/aws-sdk-go/....@v1.12.34

So to add those new services, this is indeed the commands you ran, i.e:

govendor fetch github.com/aws/aws-sdk-go/service/mediastore@v1.12.34
govendor fetch github.com/aws/aws-sdk-go/service/medialive@v1.12.34
govendor fetch github.com/aws/aws-sdk-go/service/mediaconvert@v1.12.34
govendor fetch github.com/aws/aws-sdk-go/service/mediapackage@v1.12.34
govendor fetch github.com/aws/aws-sdk-go/service/mediastoredata@v1.12.34

Thus, can you rebase against master & rerun the 5 above with the 1.12.35 tag?

Thanks!

[atsushi-ishibashi]

@Ninir Creating new branch is easier than resolving conflicts with rebasing so please check out #2481 and close this PR:bow:

[radeksimko]

#2481 was merged, so I'm going to close this. Thanks for the PR.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!