Skip to content
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.

refactor(oauth): Remove support for migration=amo #6131

Merged
merged 1 commit into from Apr 30, 2018

Conversation

shane-tomlinson
Copy link

migration=amo will not cause an error, but no special
help text is displayed either. The value is dropped on
the ground.

fixes #6123

Before merging, we need to find out if AMO still sends this query parameter. It doesn't seem like it when doing a quick query on DataDog.

@shane-tomlinson shane-tomlinson self-assigned this Apr 27, 2018
@ghost ghost added the waffle:active label Apr 27, 2018
@shane-tomlinson
Copy link
Author

From mozilla/addons#3839:

I don't think this is useful anymore since we migrated to FxA a loooong time ago and I don't recall any recent migration issues.

And their integration was closed. migration=amo isn't being used!

`migration=amo` will not cause an error, but no special
help text is displayed either. The value is dropped on
the ground.

fixes #6123
@shane-tomlinson shane-tomlinson changed the title [WIP] refactor(oauth): Remove support for migration=amo refactor(oauth): Remove support for migration=amo Apr 30, 2018
@shane-tomlinson
Copy link
Author

@mozilla/fxa-devs - r?

@shane-tomlinson shane-tomlinson removed their assignment Apr 30, 2018
@vladikoff vladikoff merged commit 8f884aa into master Apr 30, 2018
@vladikoff vladikoff deleted the issue-6123-remove-amo-migration branch April 30, 2018 15:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Do we still need the AMO migration feature?
2 participants