Skip to content

Conversation

@stsewd
Copy link
Member

@stsewd stsewd commented Mar 2, 2023

In .com need to check for this.
But we don't allow users to create custom domains if they don't have the right subscription, so not sure if this is really needed.. It can be useful only if a user downgrades their subscription I guess.

In .com need to check for this.
But we don't allow users to create custom domains if they don't have
the right subscription, so not sure if this is really needed..
It can be useful only if a user downgrades their subscription I guess.
@stsewd stsewd requested a review from a team as a code owner March 2, 2023 17:19
@stsewd stsewd requested a review from benjaoming March 2, 2023 17:19
@stsewd stsewd requested a review from ericholscher March 2, 2023 17:19
Copy link
Member

@humitos humitos left a comment

Choose a reason for hiding this comment

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

I think this looks good from the backend perspective. However, we should have some better UX here as well. That is,

  • if the user wants to downgrade, we should alarm they about this
  • if they stop paying us for some reason, their whole site will fail immediately -- not good
  • something else to think about?

That said, have you thought about these things already and how we can handle?

@stsewd
Copy link
Member Author

stsewd commented Mar 2, 2023

if they stop paying us for some reason, their whole site will fail immediately -- not good

Their site will keep working, this change matches the current behavior, we just stop redirecting to their canonical domain if users visit their docs to a non-canonical domain.

@stsewd
Copy link
Member Author

stsewd commented Mar 2, 2023

if the user wants to downgrade, we should alarm they about this

I think downgrading happens in the stripe UI, not sure what stripe shows there currently

Copy link
Member

@humitos humitos left a comment

Choose a reason for hiding this comment

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

I think it's fine to move forward with this for now. @stsewd could you open an issue if there is no one already opened to handle the questions I raised here?

@stsewd stsewd merged commit 96fe669 into main Mar 6, 2023
@stsewd stsewd deleted the fix-cname-check-corp branch March 6, 2023 19:01
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.

3 participants