Regex in type configuration prevents using Cloudformation dynamic references.

[kiwi-33]

The string validation for the OpsgenieApiKey value in the configuration schema of the cloudformation extension is:

"OpsgenieApiKey": {
          "type": "string",
          "pattern": "[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}"
        }

With this strict check, it is not possible to use cross-account dynamic references using template values. The advice for defining account level configuration advises to use dynamic references. Without this, any secret API key is compromised as users within an AWS account will be able to navigate to the cloudformation extension and view the secret value in plain text in the extension configuration.

Can the schema be updated to remove this validation? Or at least also support some pattern like\{\{.*\}\} that will allow template values in this format {{resolve:secretsmanager:arn:aws:secretsmanager:region:123456789012:secret:secretname:SecretString:key}} ?

[skanda9999]

@kiwi-33 The schema is updated to check for both the API key and dynamic references.
https://opsgeniedownloads.s3.us-west-2.amazonaws.com/cloudformation/atlassian-opsgenie-integration-v2.1.2.zip
https://opsgeniedownloads.s3.us-west-2.amazonaws.com/cloudformation/atlassian-opsgenie-team-v2.1.2.zip
https://opsgeniedownloads.s3.us-west-2.amazonaws.com/cloudformation/atlassian-opsgenie-user-v2.1.2.zip