should truncate large env vars in osc describe

[sosiouxme]

For things with certs and such in env vars, the output should be truncated by default, expanded by option.

# osc describe dc router
Name:           router
Created:        19 hours ago
Labels:         router=router
Latest Version: 1
Strategy:       Recreate
Triggers:
        - ConfigChange
                <no options>
Template:
        Selector:       router=router
        Replicas:       1
        Containers:
                NAME    IMAGE                                                                                           ENV
                router  docker-buildvm-rhose.usersys.redhat.com:5000/openshift3_beta/ose-haproxy-router:v0.4.3.2        OPENSHIFT_CA_DATA=-----BEGIN CERTIFICATE-----
MIIC5jCCAdCgAwIBAgIBATALBgkqhkiG9w0BAQswJjEkMCIGA1UEAwwbb3BlbnNo
aWZ0LXNpZ25lckAxNDI5MDMxODYxMB4XDTE1MDQxNDE3MTc0MloXDTE2MDQxMzE3
[... a whole lot of this ...]
ntIQ+PfXWZEN1Nt5EPWjl0ep911MUIEFTf7kIfiXWtCPS5W41D9tqUYZe7oNfwID
iibmeJqpn8X+PzkuSJ2j1+XCdL2b+Zc38rYUc5V62GPNytagCEpo
-----END RSA PRIVATE KEY-----
,OPENSHIFT_MASTER=https://172.16.4.164:8443
Latest Deployment:
        Name:           router-1
        Status:         Complete
        Selector:       deployment=router-1,deploymentconfig=router,router=router
        Labels:         router=router
        Replicas:       1 current / 1 desired
        Pods Status:    1 Running / 0 Waiting / 0 Succeeded / 0 Failed

[jwforres]

this would require a "verbose" option on describe CC @fabianofranz

[jwforres]

We have similar problems with really long annotation values, but considering just trimming these for now

[sosiouxme]

Also build descriptions in osc status possibly.

Since describe code is mostly upstream and "verbose" would mean adding yet another parameter to propagate throughout the stack, we sort of concluded it might be best to truncate everything unconditionally and let them use get -o yaml for verbose.

[fabianofranz]

This could be a quick solution for the moment and avoid the need of a "verbose" flag:

Template:
        Selector:       router=router
        Replicas:       1
        Containers:
                NAME    IMAGE                                                                                           ENV
                router  docker-buildvm-rho... [1]        OPENSHIFT_CA_DA... [2]

[1] docker-buildvm-rhose.usersys.redhat.com:5000/openshift3_beta/ose-haproxy-router:v0.4.3.2

[2] OPENSHIFT_CA_DATA=-----BEGIN CERTIFICATE-----
MIIC5jCCAdCgAwIBAgIBATALBgkqhkiG9w0BAQswJjEkMCIGA1UEAwwbb3BlbnNo
aWZ0LXNpZ25lckAxNDI5MDMxODYxMB4XDTE1MDQxNDE3MTc0MloXDTE2MDQxMzE3
[... a whole lot of this ...]
ntIQ+PfXWZEN1Nt5EPWjl0ep911MUIEFTf7kIfiXWtCPS5W41D9tqUYZe7oNfwID
iibmeJqpn8X+PzkuSJ2j1+XCdL2b+Zc38rYUc5V62GPNytagCEpo
-----END RSA PRIVATE KEY-----

[openshift-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close