jkremser/Generate OLM manifests
Action for generating OLM bundle manifests
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| cloneRepo | Whether to clone the git repo specified by repoURL and targetRevision | — | true |
| repoURL | Git repository | yes | — |
| targetRevision | Specific commit, tag or branch in given git repository. Defaults to HEAD | — | HEAD |
| localPath | Relative path in the repository that should be set as the CWD | no | — |
| bundleVersion | Version of the bundle that should be generated | yes | — |
| crdsDir | Relative path on the repo to the crds | yes | — |
| validateBundle | If "true", operator-sdk bundle validate will be run. Requires docker to be installed on the image. | no | false |
| validateKustomize | If "true", kustomize build will be run on config/manifests/ | no | true |
| deployDir | Relative path on the repo to the deployment yaml manifests | yes | — |
| helmCommand | Use this command to render the deployment yamls for the operator (when using Helm chart). Redirect the output to the file under {deployDir} | no | — |
| operatorName | Under this name we create the PR against the upstream community-operators repo | no | — |
| prepareHelmCommand | Use this to run helm update for instance | no | — |
| postGenerateHook | Run these commands after operator-sdk has created the bundle files. Perhaps add additional metadata etc. yq is installed on the container image | — | — |
| preGenerateHook | Run these commands before operator-sdk has created the bundle files. Prepare the directory structure, files. | — | — |
| operatorSdkVersion | Version of the operator-sdk (https://github.com/operator-framework/operator-sdk/releases) | no | v1.13.0 |
Outputs
| name | description |
|---|---|
| treeOutput | The result running tree command on the newly created bundle directory |
| csvOutput | Text representation of the ClusterServiceVersion manifest |