Skip to content

Conversation

@zawadzkidiana
Copy link
Contributor

Added validation in the domain handler to reject UpdateDomain requests when the domain status is DEPRECATED.

Why?

Deprecated domains should not be modified. Previously, UpdateDomain would accept requests for deprecated domains, which could lead to:

  • Unintended configuration changes to domains that are no longer in use
  • Confusion about domain lifecycle state
  • Potential issues during domain cleanup operations

How did you test it?

  • Added unit test TestUpdateDomain_DeprecatedDomain_ReturnsError to verify deprecated domains cannot be updated
  • Existing domain handler tests continue to pass
  • All 4626 tests in common/domain package pass

Potential risks

Low risk. This change only affects deprecated domains, which are not actively processing workflows. The change is defensive and prevents unintended modifications.

Normal domain operations (registered, active domains) are completely unaffected.

Release notes

  • Domain handler now rejects UpdateDomain requests for deprecated domains with a clear error message

UpdateDomain now returns an error when attempting to update a domain
with DEPRECATED status, preventing unintended modifications to
deprecated domains.

Changes:
- Add errDomainDeprecated error constant
- Check domain status before applying updates
- Add test case to verify deprecated domain updates are rejected

Signed-off-by: Diana Zawadzki <[email protected]>
@zawadzkidiana zawadzkidiana force-pushed the fix/domain-handler-reject-deprecated branch from 3ed70f6 to f67ba93 Compare November 13, 2025 00:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants