* 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>
This consists of two sections in the existing page:
* How to write a function
* How functions work
The former is somewhat light, because I intend to add detailed guides
for each language we support. It's hard to go too deep in this general
documentation without using language-specific examples.
Signed-off-by: Nic Cope <nicc@rk0n.org>
I plan to use the same page to document how to write a composition
function. I'll add that documenation in a future commit.
Signed-off-by: Nic Cope <nicc@rk0n.org>
This updates all current documentation of Composition Functions in the
master directory to reflect the new v1beta1 implementation.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Guillaume Dupin
Nic Cope
Bob Haddleton
MisterMX
Pieter Germishuys
Lucas Caparelli
Nicholas Morey
Pete Lumbis
Shubham Girdhar
Erik Godding Boye
Hasan Turken
Dr. Stefan Schimanski
Cem Mergenci
Lovro Sviben
Philippe Scorsolini
James Dobson
Yonatan Koren
Jean du Plessis