-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deleted domains block a domain application with the same name from being approved #1264
Comments
This ticket has been story pointed and meets DoR criteria. Moving to "Ready". |
This shouldn't have been marked as ready. There is an open question on, if we do this, do we want to do anything else to show how these two domains are different. This is alluded to in the additional context. Priority wise, is this really a medium? (do within the next few sprints)? |
During refinement, we talked about how we want to resolve this. We could rename the older name or have a new state, a delete-archive-tombstone thing. @abroddrick will think about and update. 🧠 |
Per refinement meeting, this ticket needs @abroddrick to update (scope and ACs) and re-story point. |
We approved a domain name that was previously deleted, and "solved" it by renaming the deleted domain. See Slack thread. When we complete this issue, an A/C should likely be to rename the deleted domain back to what it was. |
Discussed in eng huddle and the proposed solution is to use a Unique Constraint with condition. |
Current Behavior
If you have a domain in the status of deleted, then have a domain application with the domain name as the same name, you cannot approve that application because it looks like that domain already exists.
Expected Behavior
An analyst should be able to approve a domain application that just happens to have the same name as a different domain that has already been deleted
Steps to Reproduce
1.create a domain in the status of deleted
2. make a domain application have that domain name
3. approve the domain application
4. see error
AC
Environment
No response
Additional Context
The following are notes for implementation based on previous instructions, use your best judgment as these aren't AC, you may find you want to make different changes when evaluating this ticket:
You need to go through the whole codebase to find any time we are getting the domain (or domain info) object by domain name because we want to avoid an error occurring where our code expected only one domain returned but 2 are returned. There may not be any case of this, as we should be using pks, but definitely take the time to double check this.
Issue Links
Related to: #804
The text was updated successfully, but these errors were encountered: