Support proposalIdRef in GatewayAssociation (directconnect.aws.m.upbound.io/v1beta1)

[vronnG-dw]

What problem are you facing?

Description
In helm-charts/aws-config/templates/vpn-gateway.yaml, the GatewayAssociation resource currently uses a static proposalId field instead of a reference-based field.
Current behavior:

apiVersion: directconnect.aws.m.upbound.io/v1beta1
kind: GatewayAssociation
spec:
  forProvider:
    proposalId: {{ $proposalId }}

This will allow the GatewayAssociation acceptance resource to reference the proposal created by the chart instead of requiring a hardcoded/static proposal ID.

What could help solve your problem?

In GatewayAssociation replace proposalId with proposalIdRef:

apiVersion: directconnect.aws.m.upbound.io/v1beta1
kind: GatewayAssociation
spec:
  forProvider:
    proposalIdRef:
       name: <proposal-resource-name>
       namespace: <>

Why this is needed

• Removes manual dependency on external IDs
• Aligns with Crossplane reference-based composition style
• Improves portability and GitOps reliability
• Prevents race/mismatch issues between gateway creation and VIF attachment