-o json doesn't produce JSON formatted output

[ekquasar]

The command using -o json still produces table-formatted output:

> fsoc -o json uql "FETCH id FROM entities(k8s:workload)"

✓ Platform API call (POST /monitoring/v1/query/execute)
 id                                            
===============================================
 k8s:deployment:JT6tRLs2ODen18HIbDIB1w         
 k8s:deployment:b6N73TQ4P0CPIzgOXcJ59Q         
 k8s:deployment:Ez43uF6+O4qSdb1JCHzn/Q         
 k8s:deployment:KdZMpMLAMBu5pr9fr+thQg         
 k8s:deployment:dLbyCKq/OSChG8DXlHC7sg         
 k8s:deployment:4we+hv8mPpOqzQpFV7DE+g
...

Using latest FSOC:

> fsoc version

fsoc version 0.37.0

While moving the -o json to the end of the command works:

> fsoc uql "FETCH id FROM entities(k8s:workload)" -o json

✓ Platform API call (POST /monitoring/v1/query/execute)                      
{                                                                            
    "model": {                                                               
        "id": "string"                                                       
    },                                                                       
    "data": [                                                                
        {                                                                    
            "id": "k8s:deployment:JT6tRLs2ODen18HIbDIB1w"                    
        },                                                                   
        {                                                                    
            "id": "k8s:deployment:b6N73TQ4P0CPIzgOXcJ59Q"                    
        },                                                                   
        {                                                           
...

, the above is still a bug IMHO.

[pnickolov]

Thank you @ekquasar ; will look into this. The UQL commands override the -o flag, so I expect this may be caused by this interaction.

[pnickolov]

@ekquasar , following up on this, I believe this is a cobra limitation, see https://umarcor.github.io/cobra/#concepts. If not satisfied enough to close this issue, LMK and I will look further.

[ekquasar]

Fair enough. Nonetheless, from a user standpoint, it looks like Cisco code is broken whether or not it's a dependency issue.

Maybe just drop the -o json option from the CLI documentation if it doesn't work?

[pnickolov]

@ekquasar, following up on this: I agree the dependency behavior doesn't excuse it.
Strictly, nothing is broken as fsoc help uql provides the usage of fsoc uql [flags] (not fsoc [flags] uql [flags]).

That said, I will look into this when possible, as it will be better if we can support this usage form as well.

[forrestdevelops]

@pnickolov Can I pick this up?

[ekquasar]

fsoc solution download <solution-name> -o json | jq fails.

Still buggy, but when it works it's a crucial feature - super productivity gain. Oh you injure me so, FSOC.