crossplane
/
docs
mirror of https://github.com/crossplane/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix sneaky Vale spelling errors 

Signed-off-by: Nic Cope <nicc@rk0n.org>
This commit is contained in:
Nic Cope 2023-11-01 10:21:53 -07:00
parent 06d7247c8b
commit acf6be56d4
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
content/knowledge-base/guides/write-a-composition-function-in-go.md
View File

@ -430,11 +430,11 @@ for the SDK.
You can test your function by adding unit tests, and by using the `crossplane You can test your function by adding unit tests, and by using the `crossplane
beta render` command. It's a good idea to do both. beta render` command. It's a good idea to do both.
Go has rich support for unit testing. When you initialize a function from Go has rich support for unit testing. When you initialize a function from the
function-template-go it adds some unit tests to `fn_test.go`. These tests template it adds some unit tests to `fn_test.go`. These tests follow Go's
follow Go's [recommendations](https://github.com/golang/go/wiki/TestComments). [recommendations](https://github.com/golang/go/wiki/TestComments). They use only
They use only [`pkg/testing`](https://pkg.go.dev/testing) from the Go standard [`pkg/testing`](https://pkg.go.dev/testing) from the Go standard library and
library and [`google/go-cmp`](https://pkg.go.dev/github.com/google/go-cmp/cmp). [`google/go-cmp`](https://pkg.go.dev/github.com/google/go-cmp/cmp).
To add test cases, update the `cases` map in `TestRunFunction`. Expand the below To add test cases, update the `cases` map in `TestRunFunction`. Expand the below
block to view the full `fn_test.go` file for the function. block to view the full `fn_test.go` file for the function.
@ -821,9 +821,9 @@ up continuous integration (CI) using
lint, test, and build your function. You can see how the template configures CI lint, test, and build your function. You can see how the template configures CI
by reading `.github/workflows/ci.yaml`. by reading `.github/workflows/ci.yaml`.
The CI workflow can automatically push packages to xpkg.upbound.io. For this to The CI workflow can automatically push packages to `xpkg.upbound.io`. For this
work you must create a repository at https://marketplace.upbound.io. Give the CI to work you must create a repository at https://marketplace.upbound.io. Give the
workflow access to push to the Marketplace by creating an API token and CI workflow access to push to the Marketplace by creating an API token and
[adding it to your repository](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository). [adding it to your repository](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository).
Save your API token access ID as a secret named `XPKG_ACCESS_ID` and your API Save your API token access ID as a secret named `XPKG_ACCESS_ID` and your API
token as a secret named `XPKG_TOKEN`. token as a secret named `XPKG_TOKEN`.