Ensure user external attribute is preserved and not set to nil
What does this MR do and why?
A recent change introduced an issue where external attribute could be nil. This could lead to problems with API responses which expect true or false. This change ensures that nil is not set and that an existing external user doesn't get overridden.
Of note, the database allows null values for this column. We may want to consider updating that as there's no reason this column should be null. Any null value can be changed to false.
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.