Merge pull request #37 from tetracionist/main

Fix for encrypted private keys
This commit is contained in:
Ytbarek Hailu
2025-08-22 09:32:51 -07:00
committed by GitHub
4 changed files with 7 additions and 4 deletions

View File

@@ -1,6 +1,9 @@
# DLSync Changelog
This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [2.4.1] - 2025-08-22
### Fixed
- Fixed issue for encrypted private key files
## [2.4.0] - 2025-08-11
### Added
- Added support for 'PIPE' object type Deployment

View File

@@ -312,8 +312,8 @@ authenticator=externalbrowser #authenticator used for the connection (optional)
warehouse=my_warehouse #warehouse to be used by the connection
role=my_role #role used by this tool
private_key_file=my_private_key_file.p8 # private key file used for the connection (optional)
private_key_file_pwd=my_private_key_password # password for the private key file (optional)
private_key_pwd=my_private_key_password # password for the private key file (optional)
JAVA_TOOL_OPTIONS ="-Dnet.snowflake.jdbc.enableBouncyCastle=true" # This must be set if using encrypted key-pair authentication
```
You also need to provide the script root directory and which profile to use. This can be provided in the command line argument or in the environment variable.

View File

@@ -1 +1 @@
releaseVersion=2.4.0
releaseVersion=2.4.1

View File

@@ -18,7 +18,7 @@ import java.util.concurrent.atomic.AtomicBoolean;
@Slf4j
public class ConfigManager {
private final static String CONFIG_FILE_NAME = "config.yaml";
private final static String[] JDBC_KEY = {"url", "account", "user", "password", "authenticator", "role", "warehouse", "db", "schema", "private_key_pwd", "private_key_file_pwd"};
private final static String[] JDBC_KEY = {"url", "account", "user", "password", "authenticator", "role", "warehouse", "db", "schema", "privateKeyFile", "privateKeyPwd"};
private final static String SCRIPT_ROOT_KEY = "SCRIPT_ROOT";
private String scriptRoot;
private String profile;