vmware-tanzu
/
velero
mirror of https://github.com/vmware-tanzu/velero.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add note about updating CRDs during development (#3784) 

Signed-off-by: Abigail McCarthy <mabigail@vmware.com>
pull/3803/head
Abigail McCarthy 2021-05-12 15:41:11 -04:00 committed by GitHub
parent 31ced582a9
commit 0775d2ae54
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
site/content/docs/main/development.md
View File

@ -29,7 +29,7 @@ Both `make lint` and `make local-lint` will only run the linter against changes.
Use `lint-all` to run the linter against the entire code base.
The default linters are defined in the `Makefile` via the `LINTERS` variable.
The default linters are defined in the `Makefile` via the `LINTERS` variable.
You can also override the default list of linters by running the command
@ -43,4 +43,12 @@ To run unit tests, use `make test`.
If you need to add or update the vendored dependencies, see [Vendoring dependencies][11].
## Using the main branch
If you are developing or using the main branch, note that you may need to update the Velero CRDs to get new changes as other development work is completed.
```
velero install --crds-only --dry-run -o yaml | kubectl apply -f -
```
[11]: vendoring-dependencies.md