chore: use workspaces to make api changes easier

[bacherfl]

This PR introduces the use of go workspaces. Before this change, anything that involves a change or addition in the apis submodule required this to be split into multiple PRs (one for the api change, then a follow up to adapt the code in the controller/webhook). A similar approach is also used in https://github.com/open-feature/flagd, so I think we could also make use of that here

[toddbaert]

Great idea!

One question: Is there any CI (particularly the release CI) that needs to be adapted for this to work? Do those flows need to init the workspace?

[bacherfl]

Great idea!

One question: Is there any CI (particularly the release CI) that needs to be adapted for this to work? Do those flows need to init the workspace?

Looking at the CI I believe that the workspace might need to be initialised here:

open-feature-operator/.github/workflows/release-please.yml

Line 125 in 2c39428

go mod tidy

although i'm not sure if the go mod tidy and make controller-gen is actually needed - do you have some background information on why this was added here?

Edit: also I noticed the workspace init was missing before the test execution, so i have added it here as well

[toddbaert]

Great idea!
One question: Is there any CI (particularly the release CI) that needs to be adapted for this to work? Do those flows need to init the workspace?

Looking at the CI I believe that the workspace might need to be initialised here:

open-feature-operator/.github/workflows/release-please.yml

Line 125 in 2c39428

go mod tidy

although i'm not sure if the go mod tidy and make controller-gen is actually needed - do you have some background information on why this was added here?

Edit: also I noticed the workspace init was missing before the test execution, so i have added it here as well

Based on blame, it's been this way for 2 years: d4abda1

It seems like this is(was?) necessary before running ... make helm-package and ... make release-manifests on the next lines. I don't see any Go dependency management or anything like that in the Makefile, so I guess that's why it's needed here? Does that make sense?

[toddbaert]

Merging this now... we're releasing today so we'll know if it works 😅

[toddbaert]

Worked fine with the workspace init. I think we could move this into the makefile to make things more self-contained, but at least everything works as is.