Skip to content

Handle .env when updating Quarkus properties #79

Open
@gsmet

Description

@gsmet

The .env file at the root of a Quarkus project can contain environment variables that configures Quarkus and so can contain env var version of the properties.

For instance QUARKUS_MY_PROPERTY or _DEV_QUARKUS_MY_PROPERTY for something that is only enabled for the dev profile.

The rule is basically that any letter will be uppercased, numbers will be left alone and anything else will be transformed to _.

Note that while simple cases might be manageable, I'm not entirely sure how we will be able to handle regexps. We might be able to handle the most common cases (and make sure we catch errors if the transformed regexp is invalid).

One difficulty will be that my-property has to be changed to MY_PROPERTY but [a-z] shouldn't be affected. Also - can be used at the end of a class of characters and in this case, it is just a - that should be replaced.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions