* shortcode to have checkmark emoji use the body font color
Signed-off-by: Pete Lumbis <pete@upbound.io>
* Replace ✔️ text with check shortcode to have color respond to color mode
Signed-off-by: Pete Lumbis <pete@upbound.io>
---------
Signed-off-by: Pete Lumbis <pete@upbound.io>
* Rewrite page to simplify, pass vale and add new top-level endpoints
Signed-off-by: Pete Lumbis <pete@upbound.io>
* updates based on suggestions in PR
Signed-off-by: Pete Lumbis <pete@upbound.io>
* remove reference to functions
Signed-off-by: Pete Lumbis <pete@upbound.io>
* remove reference to usages
Signed-off-by: Pete Lumbis <pete@upbound.io>
---------
Signed-off-by: Pete Lumbis <pete@upbound.io>
* 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>