RETEST: AETB-6-B when importing QA test from historical data

[ntknguyen]

For deployment we will run a script on CAMDBSP to remove trailing spaces from 2 email fields.

[ntknguyen]

Steps to reproduce:

1. Check out Roxboro 4A,4B,CS004A
2. Import 2023 Q2 from historical data
3. 

[ergjustin]

---

The problem occurred because of a space in the import JSON aetbEmail. The 1.0 aetbEmail validation allows space in it, but the 2.0 aetbEmail validation does not.

Suggestion: Accept the aetbEmail with space and trim extra space before saving.

If this proposal is accepted, should I apply for only aetbEmail or all emails?

[alangmaid]

Application is behaving as expected. Will use this ticket to update historical as part of migration and deployment. Need to find other AETB-6-B email address issues.

[mark-hayward-erg]

@mark-hayward-erg will add a JIRA ticket to develop a script be run as part of the CAMDBSP production migration. Will need to retest in ECMPS 2.0 after the script is run on existing data.

[mark-hayward-erg]

Blocked by https://camddevelopment.atlassian.net/browse/EASEY-421

[mark-hayward-erg]

Script used to update data in PG databases (script has been run on dev, test, beta, and perf):

UPDATE camdecmps.air_emission_testing SET aetb_email = TRIM(aetb_email), provider_email = TRIM(provider_email);

UPDATE camdecmpswks.air_emission_testing SET aetb_email = TRIM(aetb_email), provider_email = TRIM(provider_email);

COMMIT;