Skip to content

Change of behaviour in env var interpretation from 3.4.5 to 3.5.0 #45886

Closed as not planned
@devdevx

Description

@devdevx

Given an env var starting with #, when declared using @Value or @ConfigurationProperties, it isn't loaded.

Code:

@Value("${my.variable}")
String variable;

or

@Component
@ConfigurationProperties(prefix = "my")
public class ServiceNowProperties {
    private String variable;
    ....
}

ENV VAR:

MY_VARIABLE=#my_value

Expected result (and result in 3.4.5):

variable contains the string "#my_value"

Current result (3.5.0):

no value is present in the variable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: invalidAn issue that we don't feel is valid

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions