Added -o json for storage creation / deletion / waiting

[cdrage]

[kind/Enhancement]

Which functionality do you think we should update/improve?

Currently we use the below commands for VSCode for storage creation / deletion / waiting:

createStorage

odo storage create ${storageName} --path=${mountPath} --size=${storageSize} --project ${project} --app ${app} --component ${component}

deleteStorage

odo storage delete ${storage} -f --project ${project} --app ${app} --component ${component}

waitForStorageToBeGone

oc wait pvc/${storage}-${app}-pvc --for=delete --namespace ${project}

We need to implement the -o json parameter for each command's output.

Why is this needed?

Needed for json output / VSCode to consume said output.

[cdrage]

This has actually already been implemented for odo create:

github.com/openshift/odo  add-service-listing-json ✔                                                                                                                                                                                                                                                                                                                    2d
▶ ./odo storage create mystorage --path=/opt/app-root/src/storage/ --size=1Gi -o json --context ~/nodejs-ex
{"kind":"storage","apiVersion":"odo.openshift.io/v1alpha1","metadata":{"name":"mystorage","creationTimestamp":null},"spec":{"size":"1Gi"},"status":{"path":"/opt/app-root/src/storage/"}}

[kadel]

/unassign @cdrage
/area json-output

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.