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.

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

Would like to change the name of a category, what is the process for that? #475

Closed
eriknelson opened this issue Dec 6, 2021 · 4 comments

Comments

@eriknelson
Copy link

Hello, we'd like to update a name of a migration category from "Modernization & Migration" to "Migration and Modernization". Could someone help me understand what the process for that change would be, and what kind of approvals are necessary in order to apply that change?

Somehow these community operator categories are also shared by downstream OpenShift operators, see screenshot:

image

If a downstream operator specifies a Category that is also shared by the Categories specified here, will OLM simply merge them into the same category? Who are the right people to reach out to to ask these questions? I'm also available at ernelson redhat com since this issue seems to straddle both upstream operatorhub and downstream.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 6, 2022

This issue is stale because it has been open for 30 days with no activity.

@eriknelson
Copy link
Author

Any updates on this?

@camilamacedo86
Copy link
Contributor

camilamacedo86 commented Jan 6, 2022

Hi @eriknelson,

You can only use these categories: https://github.com/operator-framework/api/blob/master/pkg/validation/internal/operatorhub.go#L143-L159

To publish your project need to pass in the validator: https://github.com/operator-framework/api/blob/master/pkg/validation/internal/operatorhub.go#L21-L125

You can test locally your bundle with Operator-SDK operator-sdk bundle validate ./bundle --select-optional suite=operatorframework

These categories/checks are also used/required to publish in OCP as you find out already. So, I do not think that we can change the order of the names without causing a significant impact.

I hope that it helps you out.
Also, please feel free to ping me on the slack(cmacedo) if you need more info and help.

rayfordj added a commit to rayfordj/community-operators-prod that referenced this issue Jan 31, 2022
The intention is to rename 'Modernization & Migration' (M & M) category
to 'Migration and Modernization' (M and M).  The approach we're taking
is to first introduce 'M and M' alongside 'M & M', then reach out to
existing consumers of the 'M & M' category to switch to the 'M and M'
category, followed by later removing 'M & M' as a category.

Reference(s):
- https://issues.redhat.com/browse/MIG-980
- https://issues.redhat.com/browse/MIG-978
- k8s-operatorhub/community-operators#475
- operator-framework/community-operators#2760
- operator-framework/community-operators#2961

Signed-off-by: Rayford Johnson <rayfordj@users.noreply.github.com>
rayfordj added a commit to rayfordj/api that referenced this issue Jan 31, 2022
The intention is to rename 'Modernization & Migration' (M & M) category
to 'Migration and Modernization' (M and M).  The approach we're taking
is to first introduce 'M and M' alongside 'M & M', then reach out to
existing consumers of the 'M & M' category to switch to the 'M and M'
category, followed by later removing 'M & M' as a category.

Reference(s):
- https://issues.redhat.com/browse/MIG-980
- https://issues.redhat.com/browse/MIG-978
- redhat-openshift-ecosystem/community-operators-prod#732
- k8s-operatorhub/community-operators#475
- operator-framework/community-operators#2760
- operator-framework/community-operators#2961

Signed-off-by: Rayford Johnson <rayfordj@users.noreply.github.com>
rayfordj added a commit to rayfordj/api that referenced this issue Jan 31, 2022
The intention is to rename 'Modernization & Migration' (M & M) category
to 'Migration and Modernization' (M and M).  The approach we're taking
is to first introduce 'M and M' alongside 'M & M', then reach out to
existing consumers of the 'M & M' category to switch to the 'M and M'
category, followed by later removing 'M & M' as a category.

Reference(s):
- https://issues.redhat.com/browse/MIG-980
- https://issues.redhat.com/browse/MIG-978
- redhat-openshift-ecosystem/community-operators-prod#732
- k8s-operatorhub/community-operators#475
- operator-framework/community-operators#2760
- operator-framework/community-operators#2961

Signed-off-by: Rayford Johnson <rayfordj@users.noreply.github.com>
@camilamacedo86
Copy link
Contributor

Closing this one as sorted out based on the comment: #475 (comment)

However, please feel free to re-open this one or raise new issues if you see that fits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants