Closed stevendborrelli closed 1 month ago
This issue can be reproduced.
After the Observe Only support, we see the references of forProvider
in atProvider
. In this case we should not see the arn
reference in forProvider
. The following spec
is from v0.34.0:
spec:
deletionPolicy: Delete
forProvider:
arn: arn:aws:ssm:us-west-1:569674547146:parameter/foo
dataType: text
region: us-west-1
tags:
crossplane-kind: parameter.ssm.aws.upbound.io
crossplane-name: foo
crossplane-providerconfig: default
tier: Standard
type: String
valueSecretRef:
key: example-key
name: parameter-secret
namespace: upbound-system
managementPolicy: FullControl
providerConfigRef:
name: default
status:
atProvider:
allowedPattern: ""
arn: arn:aws:ssm:us-west-1:569674547146:parameter/foo
dataType: text
description: ""
id: foo
keyId: ""
tags:
crossplane-kind: parameter.ssm.aws.upbound.io
crossplane-name: foo
crossplane-providerconfig: default
tagsAll:
crossplane-kind: parameter.ssm.aws.upbound.io
crossplane-name: foo
crossplane-providerconfig: default
tier: Standard
type: String
version: 1
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.
This issue is being closed since there has been no activity for 14 days since marking it as stale
. If you still need help, feel free to comment or reopen the issue!
This is still an issue. Fixing it will technically be a breaking change. My suspicion is that the arn
field in the terraform provider schema has the wrong attributes set.
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.
This issue is being closed since there has been no activity for 14 days since marking it as stale
. If you still need help, feel free to comment or reopen the issue!
What happened?
SSM Parameter stores the ARN of the generated resource in
forProvider
instead ofatProvider
.How can we reproduce it?
Apply the following yaml
Then verify that the arn is in the
forProvider
section:What environment did it happen in?