Skip to content

Filtering changed behaviour from 3.3.1 #471

@peter-c-larsson

Description

@peter-c-larsson

Affected version

3.4.0 and 3.5.0

Bug description

The following code works for us in 3.3.1 when use filter on a single file in our setup. When upgrading to 3.4.0 and 3.5.0 the following code has stopped working and no filtering is taking place in our file db/changelog/db.changelog-client-secret.xml

        <resources>
            <resource>
                <filtering>true</filtering>
                <directory>src/main/resources</directory>
                <includes>
                    <include>db/changelog/db.changelog-client-secret.xml</include>
                </includes>
            </resource>
            <resource>
                <filtering>false</filtering>
                <directory>src/main/resources</directory>
                <includes>
                    <include>**</include>
                </includes>
            </resource>
        </resources>

The file that is being filtered looks like this:

  <property name="secret" value="${env.DEV_SECRET}" context="dev" />
  <property name="secret" value="${env.PROD_SECRET}" context="prod" />

With 3.3.1 the values are replaced with the correct env variables and in the newer versions it is being unchanged.

This could also be incorrect configuration that we have that has happened to have been working in previous versions and might be a variation of this bug: #453 and submitting it as a new bug in case it is a user failure where we should have configured it differently.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions