README
¶
addon-metadata-operator
Operator responsible for managing AddOn resources in OSD
Develop
Useful make commands
Install pre-commit hooks:
$ pre-commit install
Run code checks:
$ make check
Run tests:
$ make test
Regenerate manifests and CRDs (./config/crd/bases/addonsflow.redhat.openshift.io_addonmetadata.yaml) whenever you modify the AddonMetadata type:
$ make manifest
You can also use the Dockerfile.test for a more stable environment:
$ ./pr_check.sh
Adding validators
See this doc for more information on adding new validators.
Release
mtcli
The external Jenkins integration will run the build_tag.sh script after you push a tag. The script runs goreleaser, which is responsible for building the binaries and publishing them as a Github Release.
$ git tag vX.X.X
$ git push upstream --tags
A tag can't be built twice, you will need to add a new commit and a new tag referencing the latest commit.
addon-metadata-operator image
The container image is built on every merge to the master branch. The external Jenkins integration will run the build_deploy.sh script, effectively building and pushing to: https://quay.io/repository/app-sre/addon-metadata-operator.
License
Apache License 2.0, see LICENSE.
Directories
¶
| Path | Synopsis |
|---|---|
|
api
|
|
|
v1alpha1
Package v1alpha1 contains API Schema definitions for the addons v1alpha1 API group +kubebuilder:object:generate=true +groupName=addonsflow.redhat.openshift.io
|
Package v1alpha1 contains API Schema definitions for the addons v1alpha1 API group +kubebuilder:object:generate=true +groupName=addonsflow.redhat.openshift.io |
|
cmd
|
|
|
internal
|
|
|
pkg
|
|