CLI: Implement init command

[nollymar]

Parent Issue

No response

Task

The CLI should have an init command that makes the installation and configuration process smoother. So, the init should ask for:

• An URL: the dotcms instance the user wants to connect to
• User
• Password

Using the information provided, the CLI should:

• Create or update the .env file
• Create the dot-service.yml (and the .dotcms folder if not exists)
  This code can be used as reference:

String homeDirectory = System.getProperty("user.home");
this.filePath = Paths.get(homeDirectory, ".dotcms", "folder", "myfile.txt");
Files.createDirectories(filePath.getParent());
try (BufferedWriter writer = Files.newBufferedWriter(filePath)) {
            writer.write(content);
}

• Update the application.properties (if needed)
• Configure any other setting required by the CLI to run properly
• In case a user runs any command before running the init, the execution shouldn't fail with an error. The CLI should stop the execution with a warning saying that the init command should be run first.

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

Acceptance Criteria

• Implement an init command with the given details
• Provide doc and update the CLI Quick Start
• This issue should be solved with the implementation

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[nollymar]

Note to QA: when this task is implemented, please test this other card

[dcolina]

Internal QA: Passed.

After the tests performed, it is observed that all the requirements of the task are met, among which we find

• Creation of a configuration directory named .dotcms
• The dot-service.yml file where the configuration is stored
• The configuration can be updated through dotCLI
• The corresponding documentation has been updated
• If you try to run any command before configuring the CLI configuration, you will receive an error message indicating that you need to run the config command first.

[bryanboza]

Fixed, tested using the latest CLI version on npm and it is working as expected