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

Next to hard-coded environment variables support ".env" files as well #1155

Open
thahnen opened this issue Jun 11, 2024 · 0 comments · May be fixed by #1156
Open

Next to hard-coded environment variables support ".env" files as well #1155

thahnen opened this issue Jun 11, 2024 · 0 comments · May be fixed by #1156

Comments

@thahnen
Copy link

thahnen commented Jun 11, 2024

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently, we work with ".env" files managing our environment variables that should not be uploaded into Git. The plug-in cannot cope with it, and we have to run workaround scripts/commands around the actual Maven call. We want to run Maven without having to do this but for it to pick up the content of the ".env" files on its own.

If the current behavior is a bug, please provide the steps to reproduce.

%

What is the expected behavior?

Next to the environmentVariables configuration option, there is another one like environmentFile where the path to the ".env" file can be set. When the plug-in is running it is picked up and handled correctly.

Please mention your frontend-maven-plugin and operating system version.

Plug-in and OS independent.

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

Successfully merging a pull request may close this issue.

1 participant