Skip to content
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

Add new organization domain fields #376

Merged
merged 5 commits into from
Nov 11, 2024

Conversation

amygdalama
Copy link
Contributor

@amygdalama amygdalama commented Nov 8, 2024

Description

Adds fields introduced with the domain verification product (State, VerificationStrategy, VerificationToken), and OrganizationID, which is useful for parsing organization domain events.

Documentation

Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.

[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

@amygdalama amygdalama marked this pull request as ready for review November 8, 2024 01:45
@amygdalama amygdalama requested a review from a team as a code owner November 8, 2024 01:45
Copy link
Contributor

@mattgd mattgd left a comment

Choose a reason for hiding this comment

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

Looks good, just had a high level question.

Comment on lines +93 to +97
// Strategy used to verify the domain.
VerificationStrategy OrganizationDomainVerificationStrategy `json:"verification_strategy,omitempty"`

// Token used for DNS verification.
VerificationToken string `json:"verification_token,omitempty"`
Copy link
Contributor

@mattgd mattgd Nov 11, 2024

Choose a reason for hiding this comment

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

Based on your thread, is the ultimate goal to have the domain data on the organization_domain events only, but for now they also reside on the organization events?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh no, I meant that the OrganizationID specifically is mostly useful in the context of organization domain events (since in organization events or the organization API you have the ID already from the parent organization object). it's included by the API in all cases though.

for the other fields, i don't expect VerificationStrategy or VerificationToken to be widely used, but i'm including them for completeness. State on the other hand is generally useful in all cases where this struct would be used

@amygdalama amygdalama merged commit 82c0590 into main Nov 11, 2024
2 checks passed
@amygdalama amygdalama deleted the update-organization-domain-struct branch November 11, 2024 21:50
@amygdalama amygdalama mentioned this pull request Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants