wso2 / wso2/cipher-tool

File path for deployement.toml file getting null in windows

Open
#57 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
41
Forks
92
PR merge metrics
No merged PRs in 30d

Description

Description:
Steps to re-produce

  1. Execute the ciphertool.bat -Dconfigure in the windows environment
  2. Deployment path for the deployment.toml file getting null from the following code segment.
    public static String getDeploymentFilePath() {
        String configFilePath = System.getProperty(Constants.DEPLOYMENT_CONFIG_FILE_PATH);
        if (StringUtils.isEmpty(configFilePath)) {
            configFilePath = Paths.get(System.getProperty(Constants.CARBON_CONFIG_DIR_PATH),
                             Constants.DEPLOYMENT_TOML_FILE).toString();
        }
       return configFilePath;
    }

The system property is getting null and executing the default encryption flow.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing getDeploymentFilePath and the Windows ciphertool.bat -Dconfigure flow shown in the issue. Check why the deployment configuration system property is null on Windows and verify the fallback path behavior. Done means the deployment.toml path is resolved correctly instead of entering the default encryption flow.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.