Made the customer["identifier"] field no longer unique. Added a new field, "unique_identifier", based off of "identifier", which is unique.
Note: When this is pushed to production, none of the customer identifiers will be visible in the admin tool. This can be easily fixed by going to each customers page and clicking the save button. This is not necessary for future customers, just ones that were already in the database when this change is pushed (because unique_identifier is a new field that current customers do not possess yet.)
💭 Motivation and context
Organizations should not be limited in their acronym choices based on other customers.
🧪 Testing
Tested Locally.
✅ Pre-approval checklist
[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All future TODOs are captured in issues, which are referenced
in code comments.
[x] All relevant type-of-change labels have been added.
🗣 Description
Jira ticket: https://cset.atlassian.net/browse/CPD-906
Frontend changes: https://github.com/cisagov/con-pca-web/pull/390
Made the customer["identifier"] field no longer unique. Added a new field, "unique_identifier", based off of "identifier", which is unique.
Note: When this is pushed to production, none of the customer identifiers will be visible in the admin tool. This can be easily fixed by going to each customers page and clicking the save button. This is not necessary for future customers, just ones that were already in the database when this change is pushed (because unique_identifier is a new field that current customers do not possess yet.)
💭 Motivation and context
Organizations should not be limited in their acronym choices based on other customers.
🧪 Testing
Tested Locally.
✅ Pre-approval checklist
✅ Pre-merge checklist
✅ Post-merge checklist