Skip to content
This repository has been archived by the owner on Jul 30, 2021. It is now read-only.

[Community] Renaming Nexus Operator Package (remove) #1706

Merged
merged 1 commit into from
May 12, 2020
Merged

[Community] Renaming Nexus Operator Package (remove) #1706

merged 1 commit into from
May 12, 2020

Conversation

ricardozanini
Copy link
Contributor

@ricardozanini ricardozanini commented May 12, 2020

I'm renaming the Nexus Operator package to not clash with the certified one. Please, only merge this one if the counter part (#1707) will be merged as well.

Thanks submitting your Operator. Please check below list before you create your Pull Request.


Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.


New Submissions

Updates to existing Operators

  • Is your new CSV pointing to the previous version with the replaces property?
  • Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
  • Have you tested an update to your Operator when deployed via OLM?
  • Is your submission signed?

Your submission should not

  • Modify more than one operator
  • Modify an Operator you don't own
  • Rename an operator - please remove and add with a different name instead
  • Submit operators to both upstream-community-operators and community-operators at once
  • Modify any files outside the above mentioned folders
  • Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

  1. Description about the managed Application and where to find more information
  2. Features and capabilities of your Operator and how to use it
  3. Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

  • Human readable name and 1-liner description about your Operator
  • Valid category name1
  • One of the pre-defined capability levels2
  • Links to the maintainer, source code and documentation
  • Example templates for all Custom Resource Definitions intended to be used
  • A quadratic logo

Remember that you can preview your CSV here.

--

1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need

2 For more information see here

@openshift-ci-robot openshift-ci-robot added the openshift-operator An Operator targeting OpenShift / OKD label May 12, 2020
@ricardozanini ricardozanini changed the title [Community] Renaming Nexus Operator Package (remove) [Community] Renaming Nexus Operator Package and release v0.2.0 May 12, 2020
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
@ricardozanini ricardozanini changed the title [Community] Renaming Nexus Operator Package and release v0.2.0 [Community] Renaming Nexus Operator Package (remove) May 12, 2020
@mvalahtv mvalahtv self-assigned this May 12, 2020
@mvalahtv mvalahtv merged commit 89b9f11 into operator-framework:master May 12, 2020
@ricardozanini ricardozanini deleted the rename-nexus-pkg-com branch May 12, 2020 17:12
dmesser pushed a commit to dmesser/community-operators that referenced this pull request Jun 22, 2020
…ork#1706)

Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
J0zi pushed a commit to J0zi/community-operators that referenced this pull request Jul 23, 2020
…ork#1706)

Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
openshift-operator An Operator targeting OpenShift / OKD
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants