The annotations are expected to be under the "annotations" key.
Currently, the docs instruct user to use "annotation".
Copy pasting the example won't work. This can be quite confusing as
the user will continue to see function containers spin-up and the local
function instance ignored.
Signed-off-by: Jakub Ciolek <jakub@ciolek.dev>
* Remove erroneous restrictions about using data from '.status' into ToEnvironmentFieldPath
As confirmed @phisco in [Slack](https://crossplane.slack.com/archives/CEG3T90A1/p1706970216073849?thread_ts=1706970216.073849&cid=CEG3T90A1), the 'patch and transform' documentation is wrong about the impossibility to use data from `.status.atProvider` in the `fromFielPath` of the `ToEnvironmentFieldPath` patch.
This restriction is incompatible with the example in the `EnvironmentConfig` page that shows it is :
```
patches:
- type: ToEnvironmentFieldPath
fromFieldPath: status.atProvider.id
toFieldPath: vpcId
```
https://docs.crossplane.io/latest/concepts/environment-configs/#patch-an-individual-resource
Signed-off-by: Guillaume Dupin <gdupin@gmail.com>
* backport to other releases
Signed-off-by: Guillaume Dupin <gdupin@gmail.com>
---------
Signed-off-by: Guillaume Dupin <gdupin@gmail.com>
These annotations were introduced in https://github.com/crossplane/crossplane-runtime/pull/283.
Per https://github.com/crossplane/crossplane/issues/3037 folks find
these annotations hard to reason about. That's understandable, because
they're doing a lot of subtle things.
This section ended up super long, but I think this is an area where
folks really need to understand what's happening in order to make good
decisions when Crossplane refuses to proceed.
Signed-off-by: Nic Cope <nicc@rk0n.org>
* Remove mention of the RBAC manager management policy
It's going away per https://github.com/crossplane/crossplane/issues/5227
Signed-off-by: Nic Cope <nicc@rk0n.org>
* Remove mention of RBAC management policy in pod docs
Signed-off-by: Nic Cope <nicc@rk0n.org>
---------
Signed-off-by: Nic Cope <nicc@rk0n.org>
* Update lua snippet to cover additional status conditions/kinds with no status
Signed-off-by: Jordan Nimlos <jordan.nimlos@bestbuy.com>
* ArgoCD integration docs: ProviderConfig status
Signed-off-by: Jordan Nimlos <jordan.nimlos@bestbuy.com>
* remove comment from code snippet, add hint instead
Signed-off-by: Jordan Nimlos <jordan.nimlos@bestbuy.com>
---------
Signed-off-by: Jordan Nimlos <jordan.nimlos@bestbuy.com>
Co-authored-by: Jordan Nimlos <jordan.nimlos@bestbuy.com>
In reality you need this, but I don't think we need to introduce it
straight away. In the Go example we already omit the equivalent.
Signed-off-by: Nic Cope <nicc@rk0n.org>
* add redirects for removed KB section
Signed-off-by: Pete Lumbis <pete@upbound.io>
* remove outdated software guides
Signed-off-by: Pete Lumbis <pete@upbound.io>
* fix netlify redirect directive
Signed-off-by: Pete Lumbis <pete@upbound.io>
* remove old link to software pages
Signed-off-by: Pete Lumbis <pete@upbound.io>
---------
Signed-off-by: Pete Lumbis <pete@upbound.io>