Skip to content

Added guidance for configuring Cloudsmith as a private registry #34047

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

Closed
wants to merge 6 commits into from

Conversation

ciaracarey
Copy link
Contributor

@ciaracarey ciaracarey commented Jul 22, 2024

Added guidance for configuring Cloudsmith as a private registry
Cloudsmith is a Cloud Native Artifact Management Platform that supports 30+ formats and integrates with Dependabot.

Cloudsmith's support for Dependabot has been tested and we have documented it on our site: https://help.cloudsmith.io/docs/dependabot.

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • For content changes, I have completed the self-review checklist.

Cloudsmith is a Cloud Native Artifact Management Platform that supports 30+ formats and integrates with Dependabot. 

Cloudsmith's support for Dependabot has been tested and we have documented it on our site: https://help.cloudsmith.io/docs/dependabot.
Copy link

welcome bot commented Jul 22, 2024

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jul 22, 2024
Copy link
Contributor

github-actions bot commented Jul 22, 2024

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md fpt
ghec
ghes@ 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.13 3.12 3.11 3.10

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

@nguyenalex836 nguyenalex836 added content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review code security Content related to code security and removed triage Do not begin working on this issue until triaged by the team labels Jul 22, 2024
@nguyenalex836
Copy link
Contributor

@ciaracarey Thanks so much for opening a PR! I'll get this triaged for review ✨

@nguyenalex836 nguyenalex836 added the needs SME This proposal needs review from a subject matter expert label Jul 25, 2024
Copy link
Contributor

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

@nguyenalex836
Copy link
Contributor

@ciaracarey Thank you for opening a PR! Per our “About contributing to GitHub Docs” article -

We only document GitHub products, features, tools, and extensions. We may mention or link to third-party tools to demonstrate how a feature works, but we do not accept pull requests to document third-party tools or integrations unless they were codeveloped with GitHub.

For this reason, we will be closing this PR. If you would like to update our docs with content outside of third-party tools or integrations, feel free to open another PR or issue 💛

@ciaracarey
Copy link
Contributor Author

thanks @nguyenalex836
could I rewrite the PR with a reduced mention of Cloudsmith?

A few other artifact management tools were mentioned on this page, so I thought it would be helpful to our joint customers.

@nguyenalex836
Copy link
Contributor

@ciaracarey I'll check with our team to see if this would be acceptable, and will provide an update as soon as I have more info!

@nguyenalex836 nguyenalex836 removed the waiting for review Issue/PR is waiting for a writer's review label Jul 26, 2024
@nguyenalex836 nguyenalex836 reopened this Jul 26, 2024
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jul 26, 2024
@nguyenalex836 nguyenalex836 removed the triage Do not begin working on this issue until triaged by the team label Jul 26, 2024
Comment on lines +625 to +656
### Cloudsmith

For information about Cloudsmith and instructions on how to configure {% data variables.product.prodname_dependabot %} to work with Cloudsmith, see [Getting Started with Cloudsmith](https://help.cloudsmith.io/docs/welcome-to-cloudsmith-docs) and [Integrate Github Dependabot with Cloudsmith](https://help.cloudsmith.io/docs/dependabot), respectively.

#### Upstreams to remote repositories

Cloudsmith Upstreams proxy and cache dependencies into Cloudsmith from remote or public repositories. Instead of directly accessing a public repository (e.g., PyPI, Maven Central, Gradle, or NuGet), Cloudsmith proxies and caches the required dependencies. By caching packages from upstream sources, Cloudsmith ensures uninterrupted access to critical dependencies, mitigates risks associated with external service disruptions, optimizes package retrieval, and strengthens supply chain security. For more information, see [Upstreams](https://help.cloudsmith.io/docs/upstream-proxying-caching) in the Cloudsmith documentation.

If the `replaces-base` setting is set to `true`, Dependabot will use the specified Cloudsmith URL as the primary source for dependencies instead of the default public repository for that package ecosystem. This means you should configure a corresponding Cloudsmith upstream to ensure Dependabot checks Cloudsmith first for dependencies. Here's an example configuration for Python:

```yaml
version: 2
registries:
cloudsmith:
type: python-index
url: https://dl.cloudsmith.io/basic/YOUR-ORG/YOUR-REPO/python/
username: "${{ secrets.CLOUDSMITH_USER_NAME }}"
password: "${{ secrets.CLOUDSMITH_API_KEY }}"
replaces-base: true

updates:
- package-ecosystem: "pip"
directory: "/"
schedule:
interval: "daily"
registries:
- cloudsmith
commit-message:
prefix: "deps"
open-pull-requests-limit: 10
```

Copy link
Member

Choose a reason for hiding this comment

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

This seems like just a normal registry configuration for pip, no need to add an explicit example for it, I think if we just mention that Cloudsmith is supported that should be sufficient for users to figure out how to set it up.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will I make a new PR, just mentioning Cloudsmith?

Thanks again for reviewing this

Copy link
Contributor

Choose a reason for hiding this comment

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

Closing this PR given the incoming new PR 💛

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code security Content related to code security content This issue or pull request belongs to the Docs Content team needs SME This proposal needs review from a subject matter expert
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants