Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions docs/admin/guides/rbac.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/user/guides/attestation.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/
```
8 changes: 3 additions & 5 deletions docs/user/guides/host.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/user/guides/sync.md
Original file line number Diff line number Diff line change
Expand Up @@ -135,7 +135,7 @@ pulp python remote create \
]' \
--excludes '[
"django~=1.0",
"scipy"
"scipy==1.1.0"
]'
```

Expand Down
8 changes: 4 additions & 4 deletions docs/user/guides/upload.md
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down Expand Up @@ -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"
Expand All @@ -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
Expand Down Expand Up @@ -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
Expand Down
9 changes: 1 addition & 8 deletions docs/user/learn/tech-preview.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/`
Copy link
Contributor

Choose a reason for hiding this comment

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

I would add vulnerability reports as well.

- PEP 740 attestations upload and provenance syncing/serving.
Loading