-
Notifications
You must be signed in to change notification settings - Fork 67
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update render-helm-charts with example changes. (#943)
Co-authored-by: Bharath KKB <[email protected]> Co-authored-by: Awais Malik <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: g-awmalik <[email protected]> Co-authored-by: zyy98 <[email protected]> Co-authored-by: Natasha Sarkar <[email protected]> Co-authored-by: Snyk bot <[email protected]> Co-authored-by: Mengqi Yu <[email protected]> Co-authored-by: Justin Santa Barbara <[email protected]> Co-authored-by: Wietse Muizelaar <[email protected]> Co-authored-by: Christopher Fry <[email protected]> Co-authored-by: sdowell <[email protected]>
- Loading branch information
1 parent
fe4ef77
commit c2aa10b
Showing
275 changed files
with
4,881 additions
and
6,598 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -19,10 +19,10 @@ jobs: | |
- name: Install libs | ||
run: | | ||
pip install pyyaml | ||
- name: Set up Go 1.17 | ||
- name: Set up Go 1.18 | ||
uses: actions/setup-go@v2 | ||
with: | ||
go-version: 1.17 | ||
go-version: 1.18 | ||
- name: Install mdrip | ||
run: | | ||
go install github.com/monopole/[email protected] | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -42,6 +42,12 @@ check-licenses: | |
cd contrib/functions/go && $(MAKE) check-licenses | ||
cd contrib/functions/ts && $(MAKE) check-licenses | ||
|
||
add-licenses: | ||
cd functions/go && $(MAKE) add-licenses | ||
cd functions/ts && $(MAKE) add-licenses | ||
cd contrib/functions/go && $(MAKE) add-licenses | ||
cd contrib/functions/ts && $(MAKE) add-licenses | ||
|
||
verify-docs: | ||
go install github.com/monopole/[email protected] | ||
(cd scripts/patch_reader/ && go build -o patch_reader .) | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,28 +23,38 @@ be created on the [releases pages]. `RELEASE_BRANCH` is in the form of | |
`${FUNCTION_NAME}/v${MAJOR_VERSION}.${MINOR_VERSION}`. | ||
For example `set-namespace/v0.3`, `kubeval/v0.1`, etc. | ||
|
||
|
||
1. Run the script: | ||
1. Setup the release branch | ||
Release branch should have existed in the [upstream repo](https://github.com/GoogleContainerTools/kpt-functions-catalog) in the form of `<FUNCTION_NAME>/v<MAJOR>.<MINOR>`. Let's take `set-namespace/v0.4` as an example. You should replace that to your RELEASE_BRANCH. | ||
```shell | ||
> export RELEASE_BRANCH=set-namespace/v0.4 | ||
``` | ||
2. Clean up the local branch | ||
The release script needs to run in the local <RELEASE BRANCH>. To avoid git ref conflicts, we suggest you delete your local branch OR make it up to date with the remote <RELEASE BRANCH> | ||
```shell | ||
> git branch -D ${RELEASE_BRANCH} | ||
``` | ||
3. Fetch the upstream repository | ||
Your `upstream` repo should point to the official kpt-functions-catalog. Verify your git remote is set as below | ||
```shell | ||
> git remote -v | grep upstream | ||
upstream [email protected]:GoogleContainerTools/kpt-functions-catalog.git (fetch) | ||
upstream [email protected]:GoogleContainerTools/kpt-functions-catalog.git (push) | ||
# Fetch the latest upstream repo | ||
> git fetch upstream | ||
``` | ||
4. Run the doc updating script. | ||
```shell | ||
# Fetch from upstream (assuming upstream is set to official repo) | ||
git fetch upstream | ||
# Make sure local release branch is up to date | ||
# e.g. git checkout set-namespace/v0.3 && git reset --hard upstream/set-namespace/v0.3 | ||
git checkout <RELEASE_BRANCH> && git reset --hard upstream/<RELEASE_BRANCH> | ||
# Check out latest version of the make target from master | ||
git checkout upstream/master | ||
# Run the make target | ||
# e.g. RELEASE_BRANCH=set-namespace/v0.3 make update-function-docs | ||
RELEASE_BRANCH=<RELEASE_BRANCH> make update-function-docs | ||
git checkout remotes/upstream/master | ||
RELEASE_BRANCH=${RELEASE_BRANCH} make update-function-docs | ||
``` | ||
1. The script will generate a new commit in your local repository which updates | ||
the docs for the provided function release. Push this commit to your remote. | ||
5. Send out a Pull Request. | ||
Your local git reference is now pointing to the local RELEASE BRANCH. | ||
A new git commit is auto-generated which contains the function document referring to the latest function version in the form of | ||
`<FUNCTION_NAME>/v<MAJOR>.<MINOR>.<PATCH>` | ||
You should be ready to submit the Pull Request against the upstream <RELEASE_BRANCH>. | ||
```shell | ||
# Push the commit to your remote (branch name can be anything) | ||
# e.g. git push origin HEAD:update-docs-set-namespace | ||
git push origin HEAD:<remote-branch> | ||
> git push -f origin ${RELEASE_BRANCH} | ||
``` | ||
1. Create a pull request targeted at the release branch. | ||
|
||
[repo]: https://github.com/GoogleContainerTools/kpt-functions-catalog | ||
[releases pages]: https://github.com/GoogleContainerTools/kpt-functions-catalog/releases | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
BUILDER_IMAGE=golang:1.17-alpine3.15 | ||
BUILDER_IMAGE=golang:1.18-alpine3.15 | ||
BASE_IMAGE=alpine:3.15 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,2 @@ | ||
BUILDER_IMAGE=node:14.19-alpine3.15 | ||
KUBEVAL_BUILDER_IMAGE=golang:1.17-alpine3.15 | ||
BASE_IMAGE=node:14.19-alpine3.15 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.