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

generate bundle: Support overwriting of annotations.yaml #6787

Open
adambkaplan opened this issue Jul 22, 2024 · 5 comments · May be fixed by #6860
Open

generate bundle: Support overwriting of annotations.yaml #6787

adambkaplan opened this issue Jul 22, 2024 · 5 comments · May be fixed by #6860
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. language/go Issue is related to a Go operator project lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@adambkaplan
Copy link

Feature Request

Describe the problem you need a feature to resolve.

Operator bundles need to have annotations for releasing in various catalogs. These should be synced between bundle.Dockerfile and annotations.yaml, per the bundle format docs. However, operator-sdk generate bundle provides no easy means to do this. --overwrite wipes out any additional labels on the bundle.Dockerfile.

Describe the solution you'd like.

Amend --overwrite to support overwriting annotations only (or provide a new --overwrite-annotations option). Ex:

operator-sdk generate bundle --overwrite=annotations

/language go
@openshift-ci openshift-ci bot added the language/go Issue is related to a Go operator project label Jul 22, 2024
@acornett21 acornett21 added kind/feature Categorizes issue or PR as related to a new feature. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jul 22, 2024
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 21, 2024
@KeenonLee KeenonLee linked a pull request Nov 13, 2024 that will close this issue
Open
2 tasks
@KeenonLee
Copy link

Updated, Please help to take a look

@KeenonLee
Copy link

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 13, 2024
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 11, 2025
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. language/go Issue is related to a Go operator project lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

generate bundle: Support overwriting of annotations.yaml KeenonLee/operator-sdk
4 participants
@adambkaplan @openshift-bot @KeenonLee @acornett21