Add support for --output flags in config show

[FrostByte0x]

Description

Add support for output as json to config show

Fixes #196

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

As I was not sure if using a specific display option is by design for the config, this change may not be necessary to the project.

Checklist:

• My code follows the style guidelines of this project
• I have commented my code
• I ran go mod tidy
• I have added tests that prove my fix is effective or that my feature works

Changes

Current version

./ovhcloud config show -o json
┌─────────┬────────────────────┬─────────────────────┐
│ section │        key         │        value        │
├─────────┼────────────────────┼─────────────────────┤
│ default │                    │                     │
│         │ endpoint           │ ovh-eu              │
│ ovh-eu  │                    │                     │
│         │ application_key    │ aaaaaaaaaaaaa       │
│         │ application_secret │ xxxxxxxxxxxxxxx     │
│         │ consumer_key       │ yyyyyyyyyyyyyyyyyyy │
└─────────┴────────────────────┴─────────────────────┘

Updated

./ovhcloud config show -o json
{
  "default": {
    "endpoint": "ovh-eu"
  },
  "ovh-eu": {
    "application_key": "aaaaaaaaaaaaa",
    "application_secret": "xxxxxxxxxxxxxxx",
    "consumer_key": "yyyyyyyyyyyyyyyyyyy"
  }
}

[amstuta]

Thank you for your PR @FrostByte0x ! Could you just move the code you made into function RenderConfigTable ?

After that, all good to merge :)

[FrostByte0x]

Done @amstuta, please let me know if this is what you expected. Now the RenderConfigTable takes as input the output format, and if any flag is passed using -output {json|yaml|etc..}, then the fix will run instead of rendering the table.

Small update: I've moved the code block at the top of the function to not execute the Table logic.

Couple of things I've noticed:

• the same command exists in the WASM build, which I assume is for the cloud shell. We may need to bring it there as well if relevant.
• the two blocks of code that handle the data are similar. We could transform the ini as a slice of map[string]any and just use RenderTable, the tradeoff probably being that we lose the custom table setup in RenderConfigTable so it's not done for now. This may be incorrect, as I am not familiar with the project structure and how the rendering is handled.

Cheers!

[amstuta]

Thanks @FrostByte0x ! Could you check the build that is failing ?

You're right regarding the two points you mention, but I think we'll leave the code as-is for now as the WASM code to manage the config will probably be re-written soon ;)

[FrostByte0x]

Done @amstuta

I brought the same code to it. I also noticed that the cloud shell doesn't have config section, I assume it is just hidden to the user of the cloud shell

[amstuta]

Indeed, in fact right now there is nothing you can configure on the cloudshell because authentication is managed automatically, and there is no implementation made to store the preferences. It will be implemented at some point :)