The hash is needed as the dogu-op v2 violates
the go standards because it did not contain the
v2 version in the module name. Therefore an
update via 'go mod' or 'go get' is not
possible.

As the new dogu-op version do not contain the
dogu encryption functions anymore, we needed
to strip the code from encryptionAdapter.go
and delete the tests. This is no problem as
this code should be removed anyway because
we do not want to encrypt sensitive dogu config ourselves anymore.

… into feature/81-Use-Kubernetes-native-config-options-instead-of-etcd

# Conflicts:
#	go.mod
#	go.sum

this fixes further problems with the
k8s.io/client-go update

We need a wrapper because of our specific errors
in the blueprint operator. Maybe we can introduce
them in the registry-lib as well, so we can
completely remove this wrapper adapter.

For now, the plan is to replace the old etcd
adapter step by step with the new adapter.

We need a wrapper because of our specific errors
in the blueprint operator. Maybe we can introduce
them in the registry-lib as well, so we can
completely remove this wrapper adapter.

For now, the plan is to replace the old etcd
adapter step by step with the new adapter.

headers will be sent at the write call already.
Calling writeHeader cannot change the status code
afterward.

just use SensitiveDoguConfigEntryRepo directly

It was unused and it should also not be used as
it hides conflict errors which we need to handle

with the current mockery config they will not be
updated automatically with 'make mocks'. I needed
to copy the interface into another package to
generate the mocks. Then I could copy them on the
right place.

This includes the linter fixes, previously tested with
this operator.