From 0775d2ae54aff0db6dd050d4b0926d969715fcd9 Mon Sep 17 00:00:00 2001 From: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com> Date: Wed, 12 May 2021 15:41:11 -0400 Subject: [PATCH] Add note about updating CRDs during development (#3784) Signed-off-by: Abigail McCarthy --- site/content/docs/main/development.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/site/content/docs/main/development.md b/site/content/docs/main/development.md index 0a9596188..633031519 100644 --- a/site/content/docs/main/development.md +++ b/site/content/docs/main/development.md @@ -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