# OLM does not support in-place changes of the CSV, we must generate a new CSV for each change.
# With deployment by Helm chart/ArgoCD, this will result in a new CR name and the old CR name will be deleted.
# NB: this means that the CR name will typically be different in different clusters, depending on the number of changes deployed to that specific cluster.
# If we were using the OLM for deployment, we'd need to properly create new versions (see `using-olm-catalog` branch for that approach)
name:drupalsite-operator-{{ .Release.Revision }}
spec:
apiservicedefinitions:{}
customresourcedefinitions:
owned:
-displayName:"CreateDrupalwebsite"
# see https://docs.openshift.com/container-platform/4.1/applications/operator_sdk/osdk-generating-csvs.html#osdk-crds_osdk-generating-csvs
version:v1alpha1
kind:DrupalSite
name:drupalsites.drupal.webservices.cern.ch
resources:[]
specDescriptors:
-description:Which version of the [CERN Drupal distribution](https://gitlab.cern.ch/drupal/paas/composer-drupal-project) to start from
displayName:Drupal version
path:drupalVersion
x-descriptors:
# list of field rendering options in https://github.com/openshift/console/blob/b0f60e476dbd5eab74a3de76bf13d0d1c865c9bf/frontend/packages/operator-lifecycle-manager/src/components/descriptors/reference/reference.md
-'urn:alm:descriptor:com.tectonic.ui:text'
-description:Should the site become accessible to the internet?
# description: The role to require when type is `CernRole`. This role must be defined in the Application Portal (by default, a role `default-role` is created for all sites with all CERN and EduGain users).
