Fix/dx 7895 import setup backup folder path#264
Conversation
add API key validation in import/export configurations
The backup folder path was logged via log.success, which maps to the info level. For progress-supported modules like import-setup, the logger omits the console transport when showConsoleLogs is false, so the path only reached the log file and never appeared in the terminal. Print the success and backup-path messages directly via cliux.print when showConsoleLogs is false, so the path is always visible regardless of the setting. log.success is retained for the log-file record, and the direct print is guarded to avoid a duplicate line when showConsoleLogs is true.
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
Consider reviewing these vulnerabilities when fixes become available. |
| const successMessage = `Backup folder and mapper files have been successfully created for the stack using the API key ${importSetupConfig.apiKey}.`; | ||
| const backupPathMessage = `The backup folder has been created at '${pathValidator(path.join(importSetupConfig.backupDir))}'.`; |
There was a problem hiding this comment.
can we move these to messages/index.json?
There was a problem hiding this comment.
how do we resolve the variables or values used in these logs
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
Consider reviewing these vulnerabilities when fixes become available. |
3 participants
The backup folder path was logged via log.success, which maps to the info level. For progress-supported modules like import-setup, the logger omits the console transport when showConsoleLogs is false, so the path only reached the log file and never appeared in the terminal.
Print the success and backup-path messages directly via cliux.print when showConsoleLogs is false, so the path is always visible regardless of the setting. log.success is retained for the log-file record, and the direct print is guarded to avoid a duplicate line when showConsoleLogs is true.