Skip to content

fix(service-registry artifact): provide content type for export#1782

Merged
rkpattnaik780 merged 1 commit intomainfrom
artifact_export
Nov 4, 2022
Merged

fix(service-registry artifact): provide content type for export#1782
rkpattnaik780 merged 1 commit intomainfrom
artifact_export

Conversation

@rkpattnaik780
Copy link
Copy Markdown
Contributor

Closes #1774

Verification Steps

  1. Run the command to export all artifacts in a service-registry
rhoas service-registry artifact export --output-file export.zip
  1. It should create a new zip folder export.zip with all artifacts present in the Service Registry instance.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation change
  • Other (please specify)

Copy link
Copy Markdown
Contributor

@jackdelahunt jackdelahunt left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@rkpattnaik780 rkpattnaik780 merged commit f7454ce into main Nov 4, 2022
@rkpattnaik780 rkpattnaik780 deleted the artifact_export branch November 4, 2022 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Export artifacts from a Service Registry fails with a 406 Not Acceptable HTTP code

2 participants