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

Login steps outlined in every command #138

Closed
neil-hickey opened this issue Feb 22, 2018 · 3 comments
Closed

Login steps outlined in every command #138

neil-hickey opened this issue Feb 22, 2018 · 3 comments

Comments

@neil-hickey
Copy link
Member

Currently in many of the files we have a section repeated, it seems unnecessary to repeat it in so many places. We could link to another page which contains this info, or put it as a note. It doesnt add much value to each page, and makes there longer than needed.

On the command line, run the following command to log in:

pks login -a PKS_API -u USERNAME -p PASSWORD

Replace the placeholder values in the command as follows:
PKS_API is your PKS API hostname. PKS_API is the domain name you entered in Ops Manager > Pivotal Container Service > UAA > UAA URL and includes the port number for the PKS API. For example, https://api.pks.example.com:9021. The PKS API uses port 9021 by default.
USERNAME is your PKS API username. The USERNAME is the user created as a result of the Grant Cluster Access to a User step in the Manage Users in UAA topic.
PASSWORD is your PKS API password. The PASSWORD is the password created as a result of the Grant Cluster Access to a User step in the Manage Users in UAA topic.
@cf-gitbot
Copy link
Member

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

@mjgutermuth
Copy link
Contributor

Hey @neil-hickey, this step is a partial/snippet that we include in each of the "Using" topics. A lot of the user feedback showed that new operators had trouble finding these values. We'd prefer to keep the steps in-line rather than linking out and breaking the flow (that's been another common user complaint -- this makes it easy for them to get lost), but I agree that the section is too long. We can work on shortening it so it doesn't seem so cluttered.

@mjgutermuth
Copy link
Contributor

Thought about this some more and made a few adjustments based on your feedback. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants