Skip to content

Start using the new enter password url#9411

Merged
jmhooper merged 1 commit intomainfrom
jmhooper-use-enter-password-url
Oct 25, 2023
Merged

Start using the new enter password url#9411
jmhooper merged 1 commit intomainfrom
jmhooper-use-enter-password-url

Conversation

@jmhooper
Copy link
Contributor

The change in #9375 renamed the review controller to the "enter password" controller. This commit introduced a new path, but did not start using it to support the 50/50 state when that change was deployed.

This commit starts using the new path but does not remove the old ones. This is also to prevent 404s in the 50/50 state. A follow up will be needed to remove the old routes after this is deployed.

@jmhooper jmhooper requested a review from a team October 18, 2023 17:21
@jmhooper jmhooper force-pushed the jmhooper-use-enter-password-url branch from 3288e75 to 40f4e2e Compare October 18, 2023 18:36
Copy link
Contributor

@soniaconnolly soniaconnolly left a comment

Choose a reason for hiding this comment

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

LGTM. I tried this out and it works for either route.

I was surprised that going to /verify/review didn't redirect to verify/enter_password. Do you want to add those redirects?

Copy link
Contributor

Choose a reason for hiding this comment

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

As far as this PR goes, this is fine. But this code is surprising. Do we really want to redirect out of the RequestLetterController to the EnterPasswordController if the user has sent too many letters? Seems like that would be unexpected, especially if they're rate limited at the Phone step.

Copy link
Contributor

Choose a reason for hiding this comment

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

For this PR, this is fine. But it brings up the question, does it still make sense to redirect to EnterPassword here, rather than to Phone step? I think this is left over from the Flow State Machine.

The change in #9375 renamed the review controller to the "enter password" controller. This commit introduced a new path, but did not start using it to support the 50/50 state when that change was deployed.

This commit starts using the new path but does not remove the old ones. This is also to prevent 404s in the 50/50 state. A follow up will be needed to remove the old routes after this is deployed.

[skip changelog]
@jmhooper jmhooper force-pushed the jmhooper-use-enter-password-url branch from 40f4e2e to dec2364 Compare October 25, 2023 13:35
@jmhooper jmhooper merged commit 2d187eb into main Oct 25, 2023
@jmhooper jmhooper deleted the jmhooper-use-enter-password-url branch October 25, 2023 16:26
jmhooper added a commit that referenced this pull request Oct 25, 2023
In #9411 we moved all traffic from the old `/verify/review` path to the new `/verify/enter_password` path. We left the old paths around so that users getting redirected by old instances would not encounter a 404 error.

Once the changes in #9411 has been deployed for a day there should not be any more users visitting `/verify/review` and we can merge this change to remove it.

[skip changelog]
jmhooper added a commit that referenced this pull request Oct 27, 2023
In #9411 we moved all traffic from the old `/verify/review` path to the new `/verify/enter_password` path. We left the old paths around so that users getting redirected by old instances would not encounter a 404 error.

Once the changes in #9411 has been deployed for a day there should not be any more users visitting `/verify/review` and we can merge this change to remove it.

[skip changelog]
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