Add docs for Registry Credentials #564
Conversation
There was a problem hiding this comment.
Pretty neat feature!
It might be useful to refer to this topic from a topic in this section:
https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-platform-for-cloud-foundry/10-2/tpcf/toc-cf-cli-index.html
| CF_DOCKER_PASSWORD=PASSWORD cf push APP-NAME --docker-image REPO/IMAGE:TAG --docker-username USER | ||
| ``` | ||
|
|
||
| By creating Registry Credentials, Admins, Org Managers, and Space Developers can save Docker credentials for reuse among developers. |
There was a problem hiding this comment.
And also App developers
There was a problem hiding this comment.
AppDeveloper isn't a role, is it?
There was a problem hiding this comment.
I don't know how you are deciding what belongs and what doesn't. If it doesn't belong in this list, that's fine. Just seemed inconsistent to me.
| The `create-org-registry-credential` and `create-space-registry-credential` commands are context sensitive and create Registry Credentials for the Organization or Space that the user is currently targeting. | ||
|
|
||
| `REGISTRY-LOCATION` must include a host name, and may include paths and/or ports; for example, `registry.example.com`, `registry.example.com/path`, `registry.example.com/path/to/repo:5000`. Protocols such as `https://` must not be included. | ||
|
|
There was a problem hiding this comment.
It would be good to have a space example to complete the set.
|
|
||
| ## <a id='using'></a> Using Registry Credentials | ||
|
|
||
| When pushing an app, Cloud Foundry determines the Registry Credential to use by the following precedence: |
There was a problem hiding this comment.
Use of "Cloud Foundry" in this topic is unclear. Are we talking about TPCF?
There was a problem hiding this comment.
Really I'm talking about Cloud Controller. What do you suggest? "The Platform"?
There was a problem hiding this comment.
Can we not say "Cloud Controller"?
There was a problem hiding this comment.
I guess I was thinking app devs wouldn't necessarily know/care about what component is doing this. It's not the important bit I was trying to convey, away--maybe the passive voice is better here?
|
I've addressed the comments--Thanks! |
No description provided.