FIX #363: Added fix for template soft deletes #372
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: cvillanueva@equinix.com cvillanueva@equinix.com
Description
This fix removes the unique attribute from the name column inside of the template table. This attribute was prevent new templates from being added - if they shared the same name. The requirement we wish to fulfill is:
The problem is that we do not hard delete records. Instead, we add a datestamp inside of the deleted_at column and then filter any records where deleted_at is not null (getTemplate).
We still need to be able to prevent users from creating new records with the same name, if the records are still active. To meet this requirement, I added the getTemplate() function to the createTemplate() function and passed the filter of name. If a record is returned, then return an error that the record exists; otherwise, proceed with creating the record.
Why is this needed
#363
Fixes: #363
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have: