Generic error when following guide

[jroper]

Following this guide:

$ operator-sdk new memcached-operator
Create cmd/manager/main.go
Create build/Dockerfile
Create deploy/service_account.yaml
Create deploy/role.yaml
Create deploy/role_binding.yaml
Create deploy/operator.yaml
Create pkg/apis/apis.go
Create pkg/controller/controller.go
Create version/version.go
Create .gitignore
Create Gopkg.toml
Run dep ensure ...
[snip]
Run dep ensure done
Run git init ...
Initialized empty Git repository in /home/jroper/go/src/github.com/jroper/memcached-operator/.git/
Auto packing the repository in background for optimum performance.
See "git help gc" for manual housekeeping.
Run git init done
$ cd memcached-operator

At this point, there's no pkg/apis/cache/v1alpha1/memcached_types.go file, though the guide implies there should be one. I try running the generate step:

$ operator-sdk generate k8s
Running code-generation for custom resource group versions: []
2018/11/12 14:22:26 failed to perform code-generation: (exit status 255)

Then I try creating pkg/apis/cache/v1alpha1/memcached_types.go with the contents specified by the guide, and I get:

$ operator-sdk generate k8s
Running code-generation for custom resource group versions: [cache:v1alpha1, ]
2018/11/12 14:25:09 failed to perform code-generation: (exit status 255)

I wish I could provide more information or work out the problem myself, but with exit status 255 being the only information about the error, I don't have much to go off. Is there a verbose mode?

[jroper]

I worked it out - I looked at an old version of the README which mentioned using --api-version and --kind with the new command, I tried that, which of course didn't work, but it gave a error message saying that those flags have been removed and that I should look at the help for the add command, which I did, and then worked out that I had to run operator-sdk add api --api-version=cache.example.com/v1alpha1 --kind=Memcached, which is missing from the current version of the guide. I'll create a PR for that, and I'll also create an issue on operator-sdk to get the uninformative error message fixed.

[hasbro17]

@jroper Thanks for reporting the issue and your PR.
This guide usually ends up lagging behind changes to the operator-sdk's own user-guide. That's the source of truth for this guide.

We only recently updated this guide but turns out we made a mistake in the order of one of the steps.
#26

In your PR can you move the section Define the Memcached spec and status after the section Add a new custom resource. That should fix it.

In the long run I think we'll probably just defer to the SDK's user-guide to avoid these kinds of issues from updating in two places.

[jroper]

Done. I should have kept on going in the guide before creating the PR :)