per environment yamlpatch override

[erpadmin]

I need to be able to specify different certs to use for NLB TLS based on environment. This is a side discussion for #5474

I have the following block in yamlpatch override @ service/copilot/service/overrides/cfn.patches.yml

# Add an TLS listener.
- op: add
  path: /Resources/NLBListenerTLS
  value:
    Metadata: 
      'aws:copilot:description': 'An TLS listener on port `443` that forwards traffic to your tasks'
    Type: AWS::ElasticLoadBalancingV2::Listener
    Properties:
      DefaultActions:
        - TargetGroupArn: !Ref NetworkLoadBalancerTargetGroupTLS 
          Type: forward
      LoadBalancerArn: !Ref PublicNetworkLoadBalancer
      Port: 443
      Protocol: TLS
      Certificates:
        - CertificateArn: <your certificate ARN>                               <----- **Is it possible to set this value based on Environment?**
      SslPolicy: ELBSecurityPolicy-TLS13-1-2-2021-06

Is it possible to use one cert for qa and one for prod?
@Lou1415926

[Lou1415926]

One thing I can think of is to use CloudFormation's Mappings section. As an example:

- op: add
   path: /Mappings
   value:
     NLBCertificates:
       qa:
         Certificate: <arn1>
       prod:
         Certificate: <arn2>
- op: add
   path: /Resources/NLBListenerTLS
   value:
     Properties:
      Certificates:
        - CertificateArn:
             Fn::FindInMap: [NLBCertificates, Ref: Env, Certificate]