Skip to content

Add source information to CCR Proxy Documentation - #1392

Merged
ryanrichter94 merged 2 commits into
chocolatey:masterfrom
imm0rtalsupp0rt:docs-maint
Oct 8, 2026
Merged

ryanrichter94 merged 2 commits into
chocolatey:masterfrom
imm0rtalsupp0rt:docs-maint

Conversation

@imm0rtalsupp0rt

Copy link
Copy Markdown
Contributor

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:

  • An info callout reminder for adding authentication and any additional options required, with an xref to the appropriate portion of the Source command if needed.
  • An example code block for removing the old CCR source and adding the new internal proxy of the CCR source in its place.

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

  • I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made

  • Minor documentation fix (typos etc.).
  • Major documentation change (refactoring, reformatting or adding documentation to existing page).
  • New documentation page added.
  • The change I have made should have a video added, and I have raised an issue for this.
    • Issue #

Change Checklist

  • Requires a change to menu structure (top or left-hand side)/
  • Menu structure has been updated
  • Images added to the img repository?
    • PR -
  • All items are complete on the Definition of Done.

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.
Comment thread src/content/docs/en-us/guides/organizations/proxying-ccr.mdx
Added descriptions of what the code pieces are doing when running them

Co-authored-by: Ryan Richter <57045117+ryanrichter94@users.noreply.github.com>
@steviecoaster

Copy link
Copy Markdown
Contributor

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)

@imm0rtalsupp0rt

Copy link
Copy Markdown
Contributor Author

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?

Adding a source doesn't change depending on the repository solution, so the tabbed interface is overkill.

Bonus points for a box they can provide what they named the feed so it's a literal copy/paste operation. (Authentication not withstanding)

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.

@ryanrichter94 ryanrichter94 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM 🚀

@ryanrichter94
ryanrichter94 merged commit 9626ebb into chocolatey:master Oct 8, 2026
1 check passed
@imm0rtalsupp0rt
imm0rtalsupp0rt deleted the docs-maint branch October 8, 2026 14:52
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

Successfully merging this pull request may close these issues.

3 participants