Project

Profile

Help

Issue #5371

closed

pulp_dev for pulp3 instructions are incorrect

Added by jaymzh over 5 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version - Debian:
master
Platform Release:
Target Release - Debian:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

The installation instructions have a 3rd step of associating an artifact with content. They claim:

```
http POST $BASE_ADDR/pulp/api/v3/content/deb/packages/ _artifact=http://localhost:24817/pulp/api/v3/artifacts/1/ filename=my_content
```

Except that using this gives:

```{
"_relative_path": [
"This field is required."
],
"architecture": [
"This field is required."
],
"description": [
"This field is required."
],
"maintainer": [
"This field is required."
],
"package_name": [
"This field is required."
],
"sha256": [
"This field is required."
],
"version": [
"This field is required."
]
}
```

It turns out one must manually add a ton of information. It seems odd to have to add that information since most of it should be known by pulp from the artifact. If it must be provided the instructions should be expanded to add that.

Further, it's unclear what `_relative_path` needs to be.

Actions #1

Updated by jaymzh over 5 years ago

It get's better. If you fill in all that data you get :

```
{
"filename": [
"Unexpected field"
]
}
```

So in fact, filename shouldn't be in the instructions.

Actions #2

Updated by mdellweg about 5 years ago

  • Status changed from NEW to MODIFIED
Actions #3

Updated by quba42 over 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF