Skip to content

Revert changes for EmailDomainDNSRecordType schema#521

Merged
BinoyOza-okta merged 1 commit into
masterfrom
OKTA-1146219-revised
Apr 8, 2026
Merged

Revert changes for EmailDomainDNSRecordType schema#521
BinoyOza-okta merged 1 commit into
masterfrom
OKTA-1146219-revised

Conversation

@BinoyOza-okta

Copy link
Copy Markdown
Contributor
  • As per the requirement modification, reverted the changes for EmailDomainDNSRecordType schema to add CAA ENUM value.

…omainDNSRecordType schema to add CAA ENUM value.
@BinoyOza-okta BinoyOza-okta self-assigned this Apr 8, 2026

@aniket-okta aniket-okta left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified and approving.

Code Review: Correctly removes CAA from EmailDomainDNSRecordType enum in both email_domain_dns_record_type.py and openapi/api.yaml. The model and spec are now in sync.

Live API Verification (dotnet-sdk-dcp.oktapreview.com): Confirmed that /api/v1/email-domains only returns TXT and CNAME DNS record types — no CAA. The revert aligns the SDK with actual API behavior.

Scope Check: DNSRecordTypeDomains (custom domains) is unaffected and retains CAA as expected per OKTA-1146219.

Unit Tests: 221 passed; 10 pre-existing failures in test_file_upload_fix.py and test_config_setter.py — unrelated to this change.

LGTM ✅

@BinoyOza-okta
BinoyOza-okta merged commit 14996a2 into master Apr 8, 2026
15 checks passed
@BinoyOza-okta
BinoyOza-okta deleted the OKTA-1146219-revised branch April 8, 2026 06:59
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