Add the ability to clear the property from EnvConfig.

EnvConfig.clear(property);

Prerequisites

Put an x in all the boxes that apply

• Are you running the latest version?
• Did you perform a cursory search?
• Have you a detailed log to share?

For more information, see the CONTRIBUTING guide.

Description

[Description of the bug or feature]

Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [and so on...]

Expected behavior: [What you expected to happen]

Actual behavior: [What actually happened]

Versions: [What version of JDK/JRE and other tools are using]

Currently, it listens for ENV var to decide which environment but it's too generic.

• Change ENV to CONFIG_ENV
• Change ENV_DIR to CONFIG_DIR

Problem

EnvConfig is currently using the library below for working with keepass databases, however the library is no longer maintained and deprecated.

<dependency>
  <groupId>de.slackspace</groupId>
  <artifactId>openkeepass</artifactId>
  <version>${openkeepass.version}</version>
</dependency>

Tasks

• Investigate if there's another library that can be replaced with
• Should be able to work with both KDBX3 and KDBX4 versions.

Prerequisites

Put an x in all the boxes that apply

• Are you running the latest version?
• Did you perform a cursory search?
• Have you a detailed log to share?

For more information, see the CONTRIBUTING guide.

Description

When I deploy in aws lambda, I get a config dir not found error. Locally, the code works fine.

Expected behavior: [What you expected to happen]
The library tries to locate the config dir in /var/task/config because it's the root in the lambda environment, but can't find it because it seems like the project root is not the same as lambda root

Actual behavior: [What actually happened]
The lib finds the dir

Versions: [What version of JDK/JRE and other tools are using]
Java 8

This is more like a plea for guidance than an issue. Has anybody deployed on lambda? If so, what did you set you CONFIG_DIR environment variable to?

Relevant log:
[2021-04-30 07:54:45.374] <5e08bf1a-dee9-41a2-90fb-3f1503d7107c>
DEBUG c.g.s.e.c.ConfigLoader - config.dir set to 'config'

ERROR c.a.a.BaseFunction - Error: 1fa9abe4-779e-42b9-8b21-69dcefe29642
com.github.sitture.env.config.ConfigException: '/var/task/config/DEV' does not exist or not a valid config directory!
at com.github.sitture.env.config.ConfigLoader.getConfigFiles(ConfigLoader.java:85)
at com.github.sitture.env.config.ConfigLoader.loadFileConfigurations(ConfigLoader.java:144)
at com.github.sitture.env.config.ConfigLoader.loadConfigurations(ConfigLoader.java:123)
at com.github.sitture.env.config.EnvConfig.(EnvConfig.java:21)
at com.github.sitture.env.config.EnvConfig.getConfig(EnvConfig.java:32)
at com.github.sitture.env.config.EnvConfig.get(EnvConfig.java:132)

Add EnvConfig.has("property") check to return a boolean.

• Add a has function
• Update Read Me docs
• Update Changelog

https://maven.apache.org/guides/mini/guide-reproducible-builds.html

Add ISSUE_TEMPLATE.md and PULL_REQUEST_TEMPLATE.md under .github/ directory.

More info can be found here https://blog.github.com/2016-02-17-issue-and-pull-request-templates/

Prerequisites

Put an x in all the boxes that apply

• Are you running the latest version?
• Did you perform a cursory search?
• Have you a detailed log to share?

For more information, see the CONTRIBUTING guide.

Description

This is only the issue running on windows.

Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [and so on...]

Expected behavior: [What you expected to happen]

Actual behavior: [What actually happened]

Versions: [What version of JDK/JRE and other tools are using]