Dynamodb writeConnectionSecretToRef does not write secret data

[timpur]

What happened?

Creaded Dynamobd with

    reason: Available
    status: "True"
    type: Ready

    reason: ReconcileSuccess
    status: "True"
    type: Synced

but no connection string written to the writeConnectionSecretToRef secret. Its created with no data?

Secret (redacted) :

apiVersion: v1
kind: Secret
metadata:
  creationTimestamp: "2021-03-05T03:26:00Z"
  name: dynamodb-my-db
  ownerReferences:
  - apiVersion: dynamodb.aws.crossplane.io/v1alpha1
    controller: true
    kind: Table
type: connection.crossplane.io/v1alpha1

How can we reproduce it?

apiVersion: dynamodb.aws.crossplane.io/v1alpha1
kind: Table
#...#
  forProvider:
    attributeDefinitions:
    - attributeName: attribute1
      attributeType: S
    keySchema:
    - attributeName: attribute1
      keyType: HASH
    provisionedThroughput:
      readCapacityUnits: 1
      writeCapacityUnits: 1
    region: ap-southeast-2
    streamSpecification:
      streamEnabled: true
      streamViewType: NEW_AND_OLD_IMAGES
  providerConfigRef:
    name: default
  writeConnectionSecretToRef:
    name: dynamodb-my-db
    namespace: #...#

What environment did it happen in?

Crossplane version: v0.17.0

[muvaf]

Seems like Table does not publish any credentials. What did you expect to see published? For example, it's URL, username and password for RDS DB Instances.

[timpur]

We'll S3 bucket publishes endpoint (full bucket name) and region. So I was expecting the same ? Since you need the full db name to access it ?

[muvaf]

@timpur sounds good. Would you like to contribute this? You'd need to add a ConnectionDetails (map[string][]byte) here to obs object that contains that information retrieved from resp object.

[cookiefission]

A slight side note to this issue for other folks who might land here from search.

If you try to use a Table object in a Composition and specify connectionDetails to generate the connection details manually, the secret is still never written (in some cases) due to the underlying tables.dynamodb.aws.crossplane.io resource never becoming synced (#637, despite the title the issue affects more than just billingMode).

[haarchri]

can you have a look in #839 - we can provide with the MR the following key/values:

  LatestStreamArn
  LatestStreamLabel
  TableArn
  TableName