Issue #3232
closed
As a user, I should be told what I have just uploaded
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"]
Updated by mihai.ibanescu@gmail.com over 5 years ago
Updated by mihai.ibanescu@gmail.com over 5 years ago
- Status changed from NEW to POST
Added by Mihai Ibanescu over 5 years ago
Added by Mihai Ibanescu over 5 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.
Added by Mihai Ibanescu over 5 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.
Added by Mihai Ibanescu over 5 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.
Updated by Anonymous over 5 years ago
- Status changed from POST to MODIFIED
Applied in changeset 18e6c1fe83e9686e54178067b0c213067975e9ee.
Added by Mihai Ibanescu over 5 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)
Added by Mihai Ibanescu over 5 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)
Updated by Anonymous over 5 years ago
Applied in changeset 908f589b3339d5ef5f6ba381c4a01070241650d0.
Updated by pcreech over 5 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
.
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