SSM Parameters should support paths in names

[stevendborrelli]

What problem are you facing?

Currently the AWS SSM parameter resource is using config.NameAsIdentifier, which means that the k8s name is used.

However, it is common in AWS SSM parameters to have path based naming like /abc/xyz/parameter. These kinds of names are not allowed in Kubernetes objects.

https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-su-create.html

How could Official AWS Provider help solve your problem?

Have a spec.forProvider.name to support path based naming.

[svscheg]

Need to investigate if we can use some another confirmation for this resource to have a spec.forProvider.name.

[stevendborrelli]

Please note that a workaround is the use the crossplane.io/external-name annotation to set the path directly. For example:

apiVersion: ssm.aws.upbound.io/v1beta1
kind: Parameter
metadata:
    annotations:
         crossplane.io/external-name: /team1/primaryRegion
spec:
  forProvider:
      dataType: text
      insecureValue: us-east
      region: us-east-1

[github-actions]

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.

[github-actions]

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!