Context qualifier matches when no context available

Good evening.

I have this line in my master changelog:

<include context="master,prod" file="generate_credentials.sql"/>

If I pass a qualifier like --contexts=dev to the command line tool, the changeset does not run, as expected.

Therefore it seems entirely logical that if I don’t pass any --contexts= qualifier at all the changeset would also not run. However, that is not the case. Am I missing something?



By default if you don’t specify a contexts= in your command line statement it will ignore all contexts tags. So it will basicly run all statements, independent of the context you declared.

So I think you should think if your use case is suited for using a context.