Update connection details for v2

Signed-off-by: Nic Cope <nicc@rk0n.org>
This commit is contained in:
Nic Cope 2025-03-28 22:05:48 -07:00
parent 89dbb4427a
commit 81f61530cf
1 changed files with 9 additions and 12 deletions

View File

@ -6,16 +6,15 @@ description: "How to create and manage connection details across Crossplane mana
## Background
When a [Provider]({{<ref "/master/concepts/providers">}}) creates a managed
resource, the resource may generate resource-specific details. These details can include
usernames, passwords or connection details like an IP address.
When a provider creates a managed resource, the resource may generate
resource-specific details. These details can include usernames, passwords or
connection details like an IP address.
Crossplane refers to this information as the _connection details_ or
_connection secrets_.
The Provider
defines what information to present as a _connection
detail_ from a managed resource.
The Provider defines what information to present as a _connection detail_ from a
managed resource.
## Connection secrets in a managed resource
@ -23,9 +22,9 @@ Creating an individual managed resource shows the connection secrets the
resource creates.
{{<hint "note" >}}
Read the [managed resources]({{<ref "/master/concepts/managed-resources">}})
documentation for more information on configuring resources and storing
connection secrets for individual resources.
Read the [managed resources]({{<ref "managed-resources">}}) documentation for
more information on configuring resources and storing connection secrets for
individual resources.
{{< /hint >}}
@ -40,6 +39,7 @@ in the
apiVersion: iam.aws.upbound.io/v1beta1
kind: AccessKey
metadata:
namespace: default
name: test-accesskey
spec:
forProvider:
@ -75,6 +75,3 @@ attribute.ses_smtp_password_v4: 44 bytes
password: 40 bytes
username: 20 bytes
```
Compositions and CompositeResourceDefinitions require the exact names of the
secrets generated by a resource.