Open wlwwu opened 3 months ago
- name: AutoScalingGroup
connectionDetails:
- type: FromFieldPath
name: arn
fromFieldPath: status.atProvider.arn
base:
apiVersion: autoscaling.aws.upbound.io/v1beta3
kind: AutoscalingGroup
metadata:
annotations:
code.roche.com/autoscaling: autoscaling/v1beta3/autoscaling-group
labels:
code.roche.com/resource-name: autoscaling-group
name: autoscalinggroup
spec:
forProvider:
capacityRebalance: true
defaultCooldown: 60
desiredCapacity: 1
forceDelete: false
healthCheckType: EC2
launchTemplate:
# id: lt-0a256d4ea88aeda2a
version: "$Latest"
maxSize: 1
minSize: 1
# serviceLinkedRoleArn: arn:aws-cn:iam::307834784563:role/crossplanerole
tag:
- key: project
propagateAtLaunch: true
value: demo
- key: env
propagateAtLaunch: true
value: dev
waitForCapacityTimeout: "0"
publishConnectionDetailsTo:
name: autoscaling-connections
configRef:
name: default
metadata:
labels:
owner: crossplane same issue in autosacling. it is not working for publishConnectionDetailsTo
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale
. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
Is there an existing issue for this?
Affected Resource(s)
rds.aws.upbound.io/v1beta1
Resource MRs required to reproduce the bug
No response
Steps to Reproduce
composition: kind: Composition apiVersion: apiextensions.crossplane.io/v1 metadata: name: xdbsubnetgroups labels: services: dbsubnetgroup spec: writeConnectionSecretsToNamespace: crossplane-connections publishConnectionDetailsWithStoreConfigRef: name: default
compositeTypeRef: apiVersion: cpc.roche.com/v1alpha1 kind: XDbSubnetGroup patchSets:
name: tags-patchset patches:
resources:
xr.yaml: apiVersion: cpc.roche.com/v1alpha1 kind: XDbSubnetGroup metadata: name: demo-dbsubnetgroup namespace: crossplane-system spec: project: demo env: dev providerConfigName: role-irsa region: cn-north-1 subnets:
after apply: kc get secrets -n crossplane-connections NAME TYPE DATA AGE 488e8a75-b1da-48f2-a45b-a2facb2bc18e connection.crossplane.io/v1alpha1 2 14m dbsubnetgroup-credentials connection.crossplane.io/v1alpha1 0 14m
What happened?
we can see that we will have two secrets created, 488e8a75-b1da-48f2-a45b-a2facb2bc18e secret is from writeConnectionSecretsToNamespace: crossplane-connections. and dbsubnetgroup-credentials secret is from publishConnectionDetailsTo....
but dbsubnetgroup-credentials connection.crossplane.io/v1alpha1 0 14m it is empty.... no data is written to the secret....
Relevant Error Output Snippet
No response
Crossplane Version
v1.16.0
Provider Version
1.9.0
Kubernetes Version
No response
Kubernetes Distribution
No response
Additional Info
No response