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.

Sign up for GitHub

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

Jump to bottom

Find underlying issue behind needing to run specific app's migrations individually #1146

Closed
scottx611x opened this issue May 17, 2016 · 2 comments
Closed

Find underlying issue behind needing to run specific app's migrations individually #1146

scottx611x opened this issue May 17, 2016 · 2 comments
Assignees
@scottx611x
Labels
database deployment technical debt

Comments

@scottx611x
Copy link
Member

These workarounds were introduced in commits: 0c4cc06 & 5641859

Steps to reproduce

  1. vagrant provision

Observed behavior

If one provisions their instance using one of these commits or later they'll see the extra steps that have been introduced.

Expected behavior

We should not need to provide these individual migration steps as they may lead to more issues down the road.
@scottx611x scottx611x added this to the Next milestone May 17, 2016
@scottx611x scottx611x self-assigned this May 17, 2016
@mccalluc
Copy link
Member

mccalluc commented Aug 5, 2016

1146

@mccalluc mccalluc mentioned this issue Aug 24, 2016
Closed
@scottx611x scottx611x mentioned this issue Aug 30, 2016
Closed
@jkmarx jkmarx removed this from the Next milestone Oct 20, 2016
@scottx611x
Copy link
Member Author

This has been addressed as of: #1511

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@scottx611x scottx611x

Labels
database deployment technical debt
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mccalluc @scottx611x @jkmarx