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

[WIP] vSphere provider update docs #6661

Closed

Conversation

chrislovecnm
Copy link
Contributor

This is for the next release

Multiple update of docs.

  • Provided link to vSphere dev docs
  • Moved testing info out of general docs
  • bumped to "alpha" release
  • created new pages for user setup

@stack72 @jen20 can I use the cool link syntax here on the website as well? Or is this github specific?

@stack72
Copy link
Contributor

stack72 commented May 13, 2016

@chrislovecnm if you cd to website and make dev then you should be able to visit the docs in your local browser at http://localhost:4567 :)

@chrislovecnm chrislovecnm changed the title vSphere provider update docs [WIP] vSphere provider update docs May 13, 2016
The VMware vSphere provider's acceptance tests require the above provider
configuration fields to be set using the documented environment variables.

## Environment Variables
Copy link
Contributor

@thetuxkeeper thetuxkeeper May 13, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VSPHERE_USER and VSPHERE_PASSWORD are missing
Sorry, missed the reference to "the above provider configuration fields".

Copy link
Contributor

@thetuxkeeper thetuxkeeper May 13, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But perhaps this could be more clear instead "above". A link or something like "[...] require the provider configuration fields mentioned in the user documentation to be set [...]"
Perhaps a little shorter, but something in that direction since there is quite much "above" (privileges, govmomi).

@stack72
Copy link
Contributor

stack72 commented Oct 26, 2016

@chrislovecnm any chance of a status update on this PR? Is this something that can be closed out?

@chrislovecnm
Copy link
Contributor Author

Closing it out

@ghost
Copy link

ghost commented Apr 21, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants