ワークスペース・デプロイメントのプロパティー

spec:
  bindings: 
    jdbccfg: workspace-application # Manage-workspace level, required. 
    #jdbcfg expects connection string, jdbc options, use SSL flag, username, password, certificate

  components: #?where do we provide the descrption of the component and get it translated? What displayed to the
              #end user are supposed to be desciption of the component, not necessarily the actual identifier on the CR
    managebase: # The components. It is a variable list. Value come from a predefined list. Some componnet have additional configuration
                # should it be a list or like that originall on the playbook
      version: 8.0.0
    nuclear:
      version: 8.0.0
    acm:
      version: 8.0.0
      bindings: #
        bdi: workspace-application # we expect bdi configuration is needed for acm and aviation.
                                   # how do we specify it is needed?
        version: latest # If latest, operator will choose the default version of the component. Where would be a possible list comfrom
                      # Manage operator maintains a supporte version of add ons based on the manage base version in the admission
                      # webhook.


  settings:
    lanaguges:
      baseLang: EN #optional base language
      secondaryLangs: #optional list of language codes, default empty
        - FR #?a code, a two leter standard? The list coming from the schema validation
        - IT
    customization:
      customizationArchive: https://company.com/customization.zip #optional customization archive that wget can obtained, no security
      customizationArchiveCredential: secretname #optional secret name and password for wget
                 #only support http, https, ftp, ftps with password authentication for now. Additonal method may be provided in the
                 #future.

    db: 
      dbSchema: maximo #optional, default to maximo, but typically need input ?should it be in jdbccfg?
      encryptionSecret: <workspaceid>-encryption-secret #?how to indicate this is a secret and have to be certain name? User enter properties, if not exist, generate default, should we use fixed name or allow user to specify secret?
      maxinst: # optional but typically the databata need to input. Cannot change after deploymet ?How to tell MAS about it?
        tableSpace: maxdata # only used when instantiate the DB, for a new database, customer has to specify it
        indexSpace: maxdata  # only used when instantiate the DB, for a new database, customer has to specify it
        installDemoData: false # default no, n/a after DB initialized
        demodata: true # whether the demo data will be installed. Default false
        db2Vargraphic: true # option when db is installed, n/a after DB initialized, only applies if the DB is db2

    deployment: 
      buildTag: 202011092887843 # actual build number or "latest" as default. Specifying the actual build number most likely a modification after
                                # intial deployment to prevent accidental change
      mode: up # up, down or adminmode
      persistentVolumes: # list of volumes
        - pvcName: forattachdoc the actual pvcname generated will be environment-workspaceid-pvcName, pass the generated name to ManageServerBundle CR
          volumeName: actual_volume_customer_created1 the valume customer created
          storageClass: nfs
          size: 50G
          mountPath: /dir #pass on to ManageServerBundle CR
        - pvcName: dropzone
          volumeName: actual_volume_customer_created2
          storageClass: nfs
          size: 10G
          mountPath: /dir2
      serverBundles:
      - name: "generic1" #name of the server, user input, no default ?required
        isDefault: true # default bundle, pointed from the luanch point of Manage.
                        # There are some criteria that isDefault has to be set to a bundle with a certain type.
        isUserSyncTarget: true #There are some criteria that isDefault has to be set to a bundle with a certain type.
        relica: 3
        bundleType: all # one of the predefined types ui, all, report, etc
        routeSubDomain: generic1 # subdomain that prefix manage.workspaceid.mange.domain.com
        bundlelevelproperties:  # let us know if a configmap or a section of properties . We just need to eventually produce a
                                # content of a java properties file formated configmap
          prop1: value1
          prop2: value2
        #bundleLevelProperties: bundlepropertiesconfigmap # optional configmap to specify bundle level maximo properties key value pair
        additionalServerConfig: serverxmlconfigmap # optional include secondary server.xml file
                                                   # need ui for user to enter a freeform text, either recorded here or become a configmap
      - name: "mycronservers"
        replica: 2
        bundletype: cron
      - name: "reportonly"
        replica: 1
        bundleType: report
        route: dataloadserver

#service binding expected for instanceid, workspaceid, ImageRegistry, registry pull secret
#oauth client registration

# BDI CR spec