Manual OpenBAS install method as described in docs.openbas.io create a partially broken installation #2202
Labels
bug
use for describing something not working as expected
regression
Label to identify the bug as a regression of previously working feature
Milestone
Description
When manually deploying OpenBAS as per instructions found in https://docs.openbas.io/latest/deployment/installation/#manual-installation, the resulting installation will not be able to locate agent binaries.
Environment
Latest OpenBAS as of writing: 1.10.1
Reproducible Steps
Follow steps here: When manually deploying OpenBAS as per instructions found in https://docs.openbas.io/latest/deployment/installation/#manual-installation, the resulting installation will run with unexpanded Maven @..@ placeholder values treated as literals.
Expected Output
All variables should be expanded.
Actual Output
When manually deploying OpenBAS as per instructions found in https://docs.openbas.io/latest/deployment/installation/#manual-installation, the resulting installation will run with unexpanded Maven @..@ placeholder values treated as literals. This will for example lead OpenBAS to think it is running version literal
@project.version@
.Additional information
Current workaround
Deleting variables from the application.properties file provided as a release artifact (e.g. in the archive in the github release) will force Spring to load values for the redacted variables that were expanded at build time.
Example:
will cause Spring to load the build-time value, for example
1.10.1
.Suggested path to resolution
Remove
@..@
placeholders from application.properties, or alternatively expand them in the file itself if the intention is to keep providing this file as part of the release artifacts. It is useful to have this file provided as it helps a user discover configuration keys, so we need to be wary that it works out of the box.Screenshots (optional)
The text was updated successfully, but these errors were encountered: