Future proof migration spec from irrelevant failures
What does this MR do?
Future proofs this migration spec from irrelevant failures.
Why was this MR needed?
The ApplicationSetting model was changed in CE, which broke this migration spec in EE.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the [merge request performance guides](http://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html) -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Edited by Michael Kozono