Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update script generating cli-reference doc #1992

Closed
kadel opened this issue Aug 6, 2019 · 3 comments
Closed

Update script generating cli-reference doc #1992

kadel opened this issue Aug 6, 2019 · 3 comments
Labels
priority/Medium Nice to have issue. Getting it done before priority changes would be great. triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@kadel
Copy link
Member

kadel commented Aug 6, 2019

script needs to be updated
see #1987 (review)
and #1987 (review)

@kadel kadel added this to For consideration in Sprint 171 via automation Aug 12, 2019
@girishramnani
Copy link
Contributor

girishramnani commented Aug 12, 2019

this part of the reference was added manually

[NOTE]
====
By default the path to the global preference file is `~/.odo/preferece.yaml`, it is stored in in the environment variable `GLOBALODOCONFIG`. You can set up a custom path by setting the value of the environment variable to a new preference path, for example `GLOBALODOCONFIG="new_path/preference.yaml"`

Run `echo "$GLOBALODOCONFIG"` to display the current value of the variable. 
====

which means as per the current location of this snippet, it should be part of the long description of the odo preference?
other option is to move it from here and add it to the dev docs as cli reference is auto-generated
@kadel

@kadel kadel added the priority/Medium Nice to have issue. Getting it done before priority changes would be great. label Aug 14, 2019
@girishramnani girishramnani added this to To do in Sprint 172 via automation Sep 3, 2019
@girishramnani girishramnani removed this from For consideration in Sprint 171 Sep 3, 2019
@girishramnani girishramnani added this to the 1.0 milestone Sep 3, 2019
@girishramnani girishramnani self-assigned this Sep 3, 2019
@girishramnani girishramnani moved this from For consideration to To do in Sprint 172 Sep 3, 2019
@girishramnani girishramnani added this to For consideration in Sprint 173 via automation Sep 25, 2019
@girishramnani girishramnani removed this from To do in Sprint 172 Sep 25, 2019
@girishramnani girishramnani moved this from For consideration to To do in Sprint 173 Sep 25, 2019
@girishramnani girishramnani removed this from To do in Sprint 173 Sep 25, 2019
@girishramnani girishramnani removed this from the 1.0 milestone Oct 9, 2019
@kadel
Copy link
Member Author

kadel commented Dec 5, 2019

/unassign @girishramnani
/close
/triage unresolved
the script is no longer used

@openshift-ci-robot
Copy link
Collaborator

@kadel: Closing this issue.

In response to this:

/unassign @girishramnani
/close
/triage unresolved
the scripts are is no longer used

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.

@openshift-ci-robot openshift-ci-robot added the triage/unresolved Indicates an issue that can not or will not be resolved. label Dec 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/Medium Nice to have issue. Getting it done before priority changes would be great. triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Development

No branches or pull requests

3 participants