Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[RFE] Add cmd to generate source yaml for skopeo sync #138

Closed
djzager opened this issue Jul 15, 2022 · 5 comments
Closed

[RFE] Add cmd to generate source yaml for skopeo sync #138

djzager opened this issue Jul 15, 2022 · 5 comments
Assignees
@djzager
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@djzager
Copy link
Contributor

djzager commented Jul 15, 2022

Introduce a new subcommand to crane, skopeo-sync-gen, that will look for and
evaulate all exported ImageStreams to determine if they images (and the
image's tags) should be migrated. If an image is internally or externally built
(ie. is not mirrored from another registry like quay|docker), then it will be
staged.
@djzager djzager added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 15, 2022
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 15, 2022
@github-actions
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

@djzager
Copy link
Contributor Author

djzager commented Jul 15, 2022

/triage accepted
/priority critical
/kind feature

@openshift-ci openshift-ci bot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/critical Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jul 15, 2022
@github-actions github-actions bot removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Jul 15, 2022
@migtools migtools deleted a comment from github-actions bot Jul 15, 2022
@djzager djzager added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 15, 2022
@djzager djzager self-assigned this Jul 15, 2022
@github-actions github-actions bot removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 15, 2022
@migtools migtools deleted a comment from github-actions bot Jul 15, 2022
@djzager djzager added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 15, 2022
@github-actions github-actions bot removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 15, 2022
@github-actions
Copy link

This issue synced with: https://issues.redhat.com/browse/MTRHO-33

This was referenced Jul 15, 2022
Closed
Closed
@djzager
Copy link
Contributor Author

djzager commented Jul 15, 2022

konveyor/enhancements#77

@djzager
Copy link
Contributor Author

djzager commented Jul 20, 2022

Closed with #140

@djzager djzager closed this as completed Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@djzager djzager

Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@djzager