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

allow wildcard in flyway.locations #1192

Closed
hohwille opened this issue Feb 2, 2016 · 8 comments
Closed

allow wildcard in flyway.locations #1192

hohwille opened this issue Feb 2, 2016 · 8 comments
Assignees
Milestone

Comments

@hohwille
Copy link

hohwille commented Feb 2, 2016

Flyway can be configured to scan multiple locations for migration scripts.
After some learning I discovered that you want to create folders for releases to get structure into larger and complex projects. However I would like to have something like this:

  • db
    • migration
      • 1.0
        • schema
          • V0001__create_schema_core.sql
          • ...
        • data
          • V0008__create_masterdata.sql
          • ...
        • test
          • V0020__create_masterdata.sql
      • 1.1
        • schema
          • ...
        • data
          • ...
        • test
          • ...
      • ...

Via Flyway locations I would like to switch e.g. test on and off:

flyway.locations=db/migration/*/schema,db/migration/*/data

This is currently not possible. Instead I would have to reverse the structure to:

  • db
    • migration
      • schema
        • 1.0
          • V0001__create_schema_core.sql
          • ...
        • 1.1
          • ...
      • data
        • 1.0
          • V0008__create_masterdata.sql
          • ...
        • 1.1
          • ...
      • test
        • 1.0
          • V0020__create_masterdata.sql
        • 1.1
          • ...

Does this feature request make sense to you? Are there other users having the same need? Would you welcome PRs for this?

@axelfontaine
Copy link
Contributor

axelfontaine commented Feb 2, 2016

Thanks for your suggestion. This is not something I plan to add a t this time as the workaround is quite easy (as you already demonstrated). I am however happy to leave this open and see if this gathers support over time.

@hohwille
Copy link
Author

hohwille commented Feb 2, 2016

The two directory layouts are not fully equivalent. Maybe you want to even lock the previous version folders in your VCS to prevent that they are changed. Also things that belong together for the current release are closer together in the first layout...

@ThiyaguE
Copy link

ThiyaguE commented Feb 2, 2016

+1

4 similar comments
@rljohnsn
Copy link

rljohnsn commented Feb 29, 2016

+1

@roni-frantchi
Copy link

roni-frantchi commented Mar 6, 2016

+1

@aquimi
Copy link

aquimi commented Jul 29, 2016

+1

@darkio14
Copy link

darkio14 commented Jul 29, 2016

+1

@suryaprabhakark
Copy link

suryaprabhakark commented Jul 19, 2019

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants