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.

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

Run stack_check after DB migrations and seeds #453

Merged
merged 1 commit into from
Aug 7, 2024

Conversation

philippthun
Copy link
Member

@philippthun philippthun commented Aug 7, 2024

Running the stack_check before the initial DB setup fails, as it waits for the database schema to be current (Sequel::Migrator.is_current?).

  • I have viewed signed and have submitted the Contributor License Agreement

  • I have made this pull request to the develop branch

  • I have run CF Acceptance Tests on bosh lite

Running the stack_check before the initial DB setup fails, as it waits for the database schema to be current (Sequel::Migrator.is_current?).
@philippthun philippthun requested review from xandroc and a team August 7, 2024 19:35
@philippthun philippthun merged commit f445c39 into develop Aug 7, 2024
2 checks passed
@philippthun philippthun deleted the stack-check-after-migrations-seeds branch August 7, 2024 21:08
Samze added a commit that referenced this pull request Aug 8, 2024
This reverts commit f445c39.

We can now run the stack checker before migrations as per
cloudfoundry/cloud_controller_ng#3925.

This is an improvement as we want to fail the stack checker before any
migrations have run so that we are not in a state where migrations
have run but the deployment has failed

Co-authored-by: Sam Gunaratne <[email protected]>
Samze added a commit that referenced this pull request Aug 14, 2024
This reverts commit f445c39.

We can now run the stack checker before migrations as per
cloudfoundry/cloud_controller_ng#3925.

This is an improvement as we want to fail the stack checker before any
migrations have run so that we are not in a state where migrations
have run but the deployment has failed

Co-authored-by: Sam Gunaratne <[email protected]>
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