Project

Profile

Help

Issue #3232

As a user, I should be told what I have just uploaded

Added by mihai.ibanescu@gmail.com about 4 years ago. Updated almost 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Docker:
Platform Release:
2.15.1
Target Release - Docker:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

It is helpful to know the unit_key data for the manifest that was uploaded
in order to facilitate further processing.

Typically, in an automated workflow, a docker image upload is immediately
followed by an image tag, and the digest is needed in that case.
The importer's upload_unit does not return any information about what got uploaded:

return {'success_flag': True, 'summary': '', 'details': {}}

The Debian and Windows plugins do this:

        unit = unit.save_and_associate(file_path, repo)
        return dict(success_flag=True, summary="",
                    details=dict(
                        unit=dict(unit_key=unit.unit_key,
                                  metadata=unit.all_properties)))

which seems more useful.

A somewhat similar pattern exists in the core's unit_association.py, where information about units that were successfully associated is present under the task's ["details"]["units_successful"]

Associated revisions

Revision 18e6c1fe View on GitHub
Added by Mihai Ibanescu about 4 years ago

upload_unit returns the unit key for what got uploaded

It is helpful to know the unit_key data for the manifest that was uploaded in order to facilitate further processing.

Typically, in an automated workflow, a docker image upload is immediately followed by an image tag, and the digest is needed in that case.

The return data is similar to what the association code returns.

closes #3232 https://pulp.plan.io/issues/3232

Revision 18e6c1fe View on GitHub
Added by Mihai Ibanescu about 4 years ago

upload_unit returns the unit key for what got uploaded

It is helpful to know the unit_key data for the manifest that was uploaded in order to facilitate further processing.

Typically, in an automated workflow, a docker image upload is immediately followed by an image tag, and the digest is needed in that case.

The return data is similar to what the association code returns.

closes #3232 https://pulp.plan.io/issues/3232

Revision 18e6c1fe View on GitHub
Added by Mihai Ibanescu about 4 years ago

upload_unit returns the unit key for what got uploaded

It is helpful to know the unit_key data for the manifest that was uploaded in order to facilitate further processing.

Typically, in an automated workflow, a docker image upload is immediately followed by an image tag, and the digest is needed in that case.

The return data is similar to what the association code returns.

closes #3232 https://pulp.plan.io/issues/3232

Revision 18e6c1fe View on GitHub
Added by Mihai Ibanescu about 4 years ago

upload_unit returns the unit key for what got uploaded

It is helpful to know the unit_key data for the manifest that was uploaded in order to facilitate further processing.

Typically, in an automated workflow, a docker image upload is immediately followed by an image tag, and the digest is needed in that case.

The return data is similar to what the association code returns.

closes #3232 https://pulp.plan.io/issues/3232

Revision 908f589b View on GitHub
Added by Mihai Ibanescu about 4 years ago

upload_unit returns the unit key for what got uploaded

It is helpful to know the unit_key data for the manifest that was uploaded in order to facilitate further processing.

Typically, in an automated workflow, a docker image upload is immediately followed by an image tag, and the digest is needed in that case.

The return data is similar to what the association code returns.

closes #3232 https://pulp.plan.io/issues/3232

(cherry picked from commit 18e6c1fe83e9686e54178067b0c213067975e9ee)

Revision 908f589b View on GitHub
Added by Mihai Ibanescu about 4 years ago

upload_unit returns the unit key for what got uploaded

It is helpful to know the unit_key data for the manifest that was uploaded in order to facilitate further processing.

Typically, in an automated workflow, a docker image upload is immediately followed by an image tag, and the digest is needed in that case.

The return data is similar to what the association code returns.

closes #3232 https://pulp.plan.io/issues/3232

(cherry picked from commit 18e6c1fe83e9686e54178067b0c213067975e9ee)

History

#2 Updated by mihai.ibanescu@gmail.com about 4 years ago

  • Description updated (diff)

#3 Updated by mihai.ibanescu@gmail.com about 4 years ago

  • Status changed from NEW to POST

#4 Updated by dalley about 4 years ago

  • Triaged changed from No to Yes

#5 Updated by Anonymous about 4 years ago

  • Status changed from POST to MODIFIED

#6 Updated by pcreech about 4 years ago

  • Platform Release set to 2.15.1

#7 Updated by Anonymous about 4 years ago

#8 Updated by pcreech about 4 years ago

  • Status changed from MODIFIED to 5

#9 Updated by pcreech almost 4 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE

#10 Updated by bmbouter almost 3 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF