diff --git a/docs/admin/guides/rbac.md b/docs/admin/guides/rbac.md index 9d5dab516..90ed85dc2 100644 --- a/docs/admin/guides/rbac.md +++ b/docs/admin/guides/rbac.md @@ -18,9 +18,6 @@ customized. The access policies for the Pulp APIs follow the same scheme as the about here: [Pulp File RBAC](site:pulp_file/docs/admin/guides/rbac/). Use the Pulp CLI to follow along with the examples here. -!!! note - This feature is currently in tech preview and is subject to change in future releases. - ## Default Index Behavior By default, the read APIs of the index are accessible to any user, authenticated or not, while the upload APIs diff --git a/docs/user/guides/attestation.md b/docs/user/guides/attestation.md index 20a8ba038..c8a2fca3c 100644 --- a/docs/user/guides/attestation.md +++ b/docs/user/guides/attestation.md @@ -87,5 +87,5 @@ API. The attestations can then be verified using tools like `sigstore` or `pypi- ```bash http $PULP_API/pypi/foo/simple/twine/ "Accept:application/vnd.pypi.simple.v1+json" | jq -r ".files[].provenance" -http $PULP_API/pypi/foo/integrity/twine/6.2.0/twine-6.2.0.tar.gz/ +http $PULP_API/pypi/foo/integrity/twine/6.2.0/twine-6.2.0.tar.gz/provenance/ ``` diff --git a/docs/user/guides/host.md b/docs/user/guides/host.md index 4bca5bdb4..3cce146a7 100644 --- a/docs/user/guides/host.md +++ b/docs/user/guides/host.md @@ -44,7 +44,7 @@ Setting the distribution's `repository` field will auto-serve the latest version Only packages present in your repository will be available from your index, but adding a remote source to your distribution will enable the pull-through cache feature. This feature allows you to install any package -from the remote source and have Pulp store that package as orphaned content. +from the remote source and have Pulp store that package in your repository. ```bash # Add remote to distribution to enable pull-through caching @@ -54,10 +54,8 @@ pulp python distribution update --name foo --remote bar !!! note Pull-through caching will respect the includes/excludes filters on the supplied remote. -!!! warning - Support for pull-through caching is provided as a tech preview in Pulp 3. - Functionality may not work or may be incomplete. Also, backwards compatibility when upgrading - is not guaranteed. +!!! note + Setting the remote on a distribution without a repository will cause requested content to be saved as orphans. !!! warning Chaining pull-through indices, having a pull-through point to another pull-through, does not diff --git a/docs/user/guides/sync.md b/docs/user/guides/sync.md index bf9dd0f9b..cb2dab88a 100644 --- a/docs/user/guides/sync.md +++ b/docs/user/guides/sync.md @@ -135,7 +135,7 @@ pulp python remote create \ ]' \ --excludes '[ "django~=1.0", - "scipy" + "scipy==1.1.0" ]' ``` diff --git a/docs/user/guides/upload.md b/docs/user/guides/upload.md index 60aa03552..c4340242d 100644 --- a/docs/user/guides/upload.md +++ b/docs/user/guides/upload.md @@ -44,7 +44,7 @@ Each artifact in Pulp represents a file. They can be created during sync or crea PKG="shelf-reader-0.1.tar.gz" # Upload it to Pulp - pulp python content upload --relative-path "$PKG" --file "$PKG" + pulp python content create --relative-path "$PKG" --file "$PKG" ``` === "Output" @@ -90,7 +90,7 @@ Each artifact in Pulp represents a file. They can be created during sync or crea ## Add content to a repository Once there is a content unit, it can be added to a repository using the `add` command. -This command requires both the `filename` and `sha256` to ensure that a specific file can be identified, +This command requires the `sha256` to ensure that a specific file can be identified, as Pulp may contain different content units with the same name. === "Run" @@ -100,7 +100,7 @@ as Pulp may contain different content units with the same name. SHA256="04cfd8bb4f843e35d51bfdef2035109bdea831b55a57c3e6a154d14be116398c" # Add the created PythonPackage content to the repository - pulp python repository content add --repository foo --filename "$PKG" --sha256 "$SHA256" + pulp python repository content add --repository foo --sha256 "$SHA256" # After the task is complete, it gives us a new repository version pulp python repository version show --repository foo @@ -144,7 +144,7 @@ This command requires the same options as the `add` command. ```bash # Remove the PythonPackage content from the repository - pulp python repository content remove --repository foo --filename "$PKG" --sha256 "$SHA256" + pulp python repository content remove --repository foo --sha256 "$SHA256" # After the task is complete, it gives us a new repository version pulp python repository version show --repository foo diff --git a/docs/user/learn/tech-preview.md b/docs/user/learn/tech-preview.md index 32ed6d8e4..736e9ca9d 100644 --- a/docs/user/learn/tech-preview.md +++ b/docs/user/learn/tech-preview.md @@ -2,12 +2,5 @@ The following features are currently being released as part of a tech preview -- New endpoint “pulp/api/v3/remotes/python/python/from_bandersnatch/” that allows for Python remote creation from a - Bandersnatch config file. -- PyPI’s json API at content endpoint ‘/pypi/\{package-name}/json’. Allows for basic Pulp-to-Pulp syncing. -- Fully mirror Python repositories provided PyPI and Pulp itself. -- `Twine` upload packages to indexes at endpoints '/simple\` or '/legacy'. -- Create pull-through caches of remote sources. -- Pulp Domain Support -- RBAC support +- Repair package metadata endpoint `/pulp/api/v3/repositories/python/python/{pulp_id}/repair_metadata/` - PEP 740 attestations upload and provenance syncing/serving.