Unable to upgrade from `3.2.12` to latest version due to SES configuration set

[apetta]

@fwang Sorry for the delay on this. So I'm actually using the get method as the email was not created with SST, it was on AWS already. Can't seem to get around this issue!

Originally posted by @apetta in #5423

I can't seem to get around this issue at all. Just tried to upgrade to "sst": "3.17.5", and still facing this challenge:

> sst dev

❯ pnpm sst deploy --stage akshaypetta
SST 3.17.5  ready!

➜  App:        wyzr-txn-sync
   Stage:      akshaypetta

~  Deploy

|  Error       EmailConfig aws:sesv2:ConfigurationSet
Expected an ID for urn:pulumi:akshaypetta::wyzr-txn-sync::sst:aws:Email$aws:sesv2/configurationSet:ConfigurationSet::EmailConfig
|  Updated     CreateTxnSync sst:aws:Function → CreateTxnSyncRole aws:iam:Role (1.0s)
|  Updated     TxnSyncCron sst:aws:Cron → TxnSyncCronHandlerRole aws:iam:Role (1.1s)
|  Updated     TxnSyncQueueSubscriberHwcxef sst:aws:QueueLambdaSubscriber → TxnSyncQueueSubscriberHwcxefFunctionRole aws:iam:Role (1.1s)

✕  Failed    

EmailConfig aws:sesv2:ConfigurationSet
Expected an ID for urn:pulumi:akshaypetta::wyzr-txn-sync::sst:aws:Email$aws:sesv2/configurationSet:ConfigurationSet::EmailConfig

I'm referencing it via const email = sst.aws.Email.get("Email", "email@example.com"); - this is an email address that was made directly on AWS, it was never deployed with SST.

I've tried sst refresh, sst deploy on both personal & dev stages but no luck!

[apetta]

Deleting the email identities on AWS and letting SST create them seems to have worked!