Permify Env Command

[zinc remnant]

Hello @heavy prawn , you can run Permify with three options: configuration file, environment variables, and flags. Therefore, the permify env command should print the configuration that results from whichever of these options is used. However, env only appears to handle environment variables (my bad, this was a misunderstanding). For this reason, changing the command to permify config would be more appropriate.

[heavy prawn]

Understood, thanks for the clarification, will make the changes

[heavy prawn]

@zinc remnant ```
Hello @jbergstroem, yes, I also think that permify env is not very descriptive. Therefore, changing it to permify config would be a better choice. What do you think, @neo773? Can this be done considering which option the configuration is read from?

The current layout already lists the env value in a column do we want to keep this layout?
So when `--config` flag is passed it would just read from that file instead of Viper's stored value

Replying here, is that okay? GitHub discussions take quite a while

[zinc remnant]

I didn't quite understand; can you explain in more detail?

[heavy prawn]

I meant this, "ENV" column

Should probably make it say "NULL" or something if not set

[zinc remnant]

It would be great if you could end up with a table like this. (I'm not sure if the last column is possible).

|--------------------|----------|------|
| meter enabled       | true           | env  |
| server grpc port    | 3478         | file |
| database engine    | postgres  | flag |
| logger output         | json           | file |```

[heavy prawn]

So a "source/origin" column? do you think this might get potentially confusing if user wants to compare with current config?

[zinc remnant]

@heavy prawn ,Why do you think this will create confusion? The 'value' part is the current configuration, and the 'origin' part shows where this was obtained from. The good side of this is, even if the same setting is provided through environment variables and flags, it will be clear which one is the current configuration.

[heavy prawn]

It was a misunderstanding from my side as I got confused, ignore it sorry

@zinc remnant With the new changes

[zinc remnant]

Yes @heavy prawn , that's exactly what I was talking about. Thanks.

[heavy prawn]

should I color the source value text to make it more distinguishable?

[zinc remnant]

I think it would be great

[heavy prawn]

Okay let's try a couple of colors

@zinc remnant what do you think about this? yellow for config blue for env and green for flag

[zinc remnant]

It looks good. Can you also change the name of the source with config to file?

[heavy prawn]

Done, also pushed the commit to github