PXP-477: [CLI] Develop the config secrets push command

[mfauzaan]

Summary

This PR adds a bunker secret edit command to the Wukong CLI, enabling users to update remote secrets via the command line interface after making changes to the local config files.

Example command usage: wukong-cli dev config push {path}

Multiple config changes:

Diff with the changes:

Ticket: PXP-477

What's Changed

Added

• Added wukong dev config push command to search for config files with the vault tag in the provided path or current path.
• Compare the local config files with the remote versions in Bunker and identify any changes made by the user.
• Prompt the user with a selection option if multiple secrets are eligible for editing.
• Display the differences between the local and remote secrets files before pushing changes, allowing users to confirm the modifications.
• Update the remote version with the user's changes upon confirmation.

[jk-gan]

can you update the completions by running cargo build --release && ./generate-completions.sh?

[onimsha]

From what I can see, this command allows to select an individual change in a secret file to apply the edit. This is similar to Git diff, however I'm wonder if we have actual case for this.

From the user's perspective, the diff merely for me to review the change, and I can either accept or deny it, plus an option to go back and making some edits. Selecting individual changes seems not practical IMHO.

Also, I don't see we're handling the case of multiple annotations. For example if there is an umbrella Elixir application, there can be more than 1 annotations, thus leading to multiple secret files . I just need the confirmation that we're not handling this case atm, to determine what would be the next step.

cc @jk-gan @mfauzaan

[jk-gan]

From what I can see, this command allows to select an individual change in a secret file to apply the edit. This is similar to Git diff, however I'm wonder if we have actual case for this.

From the user's perspective, the diff merely for me to review the change, and I can either accept or deny it, plus an option to go back and making some edits. Selecting individual changes seems not practical IMHO.

Also, I don't see we're handling the case of multiple annotations. For example if there is an umbrella Elixir application, there can be more than 1 annotations, thus leading to multiple secret files . I just need the confirmation that we're not handling this case atm, to determine what would be the next step.

cc @jk-gan @mfauzaan

I see, so the command is meant to be used with the annotation? The RFC I saw was saying "Pull the secret file from Bunker, make changes, and push new contents to update the Bunker". I think we misunderstood that.

[onimsha]

For this error.

comparing local config vs remote config...
Error - No such file or directory (os error 2)

We should add a suggestion text to ask user maybe they will need to run the wukong dev config pull first.

[mfauzaan]

For this error.

comparing local config vs remote config...
Error - No such file or directory (os error 2)

We should add a suggestion text to ask user maybe they will need to run the wukong dev config pull first.

[sauron-droid]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mfauzaan, onimsha

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jk-gan]

I got Permission denied and I don't why

[onimsha]

I got Permission denied and I don't why

Maybe don't have access to the Vault secret ? Can you access the secret using Bunker UI ?

since the possibility of this is small atm, we can address this in another PR later.