Repository navigation
Add source information to CCR Proxy Documentation - #1392
Conversation
0e85abe to
8cabd83
Compare
This commit adds information about removing the old CCR source from client machines and adding the newly configured internal proxy of the CCR to client machines in its place. It includes: - An info callout reminder for adding their authentication and any additional options the customer requires, with an xref to the appropriate portion of the Source command. - An example code block for removing the old CCR source and adding a new CCR proxy source in its place.
8cabd83 to
73745a8
Compare
Added descriptions of what the code pieces are doing when running them Co-authored-by: Ryan Richter <57045117+ryanrichter94@users.noreply.github.com>
|
Because we use a tabbed experience to highlight how to configure the feed in a specific repository server, would it not make sense to use a similar tabbed experience for the setup, since we know the shape of the url required by each provider? Bonus points for a box they can provide what they named the feed so it's a literal copy/paste operation. (Authentication not withstanding) |
Adding a source doesn't change depending on the repository solution, so the tabbed interface is overkill.
I considered implementing this, but it also felt like overkill given it's two lines of code a user would need to run. The example provided can be copy/pasted, and the user can then make any changes to that before running the code because as you mentioned they would still need to add authentication and any options they require. |
Description Of Changes
This commit adds information about removing the old CCR source from client machines and adding the newly configured internal proxy of the CCR to client machines in its place. It includes:
Motivation and Context
This was brought up by @steviecoaster to assist in the transition to (or in preparation of) our changes to the Terms of Service.
Testing
Change Types Made
Change Checklist