Create a fhir-bucket docker image

[prb112]

Is your feature request related to a problem? Please describe.
Include the fhir-bucket in the docker image

Describe the solution you'd like
Wrap fhir-bucket in its own docker image (similar to the schema tool).

The new image should be peer to ibm-fhir-server on DockerHub.

The user experience of the image should be focused on making reindex as simple as possible, however it should not preclude the usage of loading.

Describe alternatives you've considered
Include it in our ibm-fhir-server image directly.

Acceptance Criteria

1. GIVEN [a precondition]
   AND [another precondition]
   WHEN [test step]
   AND [test step]
   THEN [verification step]
   AND [verification step]

Additional context
Add any other context or screenshots about the feature request here.

[lmsurpre]

I added an alternative option under the "Describe alternatives" section which is to give fhir-bucket its own image.

[prb112]

requested the repository on DockerHub

[prb112]

agreed on ibm-fhir-bucket-tool

[lmsurpre]

opened #2913 with a suggested edit

[lmsurpre]

I tested the new image by wrapping it in a helm chart with a single kubernetes job:

apiVersion: batch/v1
kind: Job
metadata:
  name: {{ .Release.Name }}
  labels:
    chart: {{ .Chart.Name }}-{{ .Chart.Version }}
    release: {{ .Release.Name }}
    heritage: {{ .Release.Service }}
spec:
  template:
    metadata:
      labels:
        app: {{ template "name" . }}
        release: {{ .Release.Name }}
    spec:
      restartPolicy: Never
      imagePullSecrets:
        - name: {{ .Values.image.pullSecret }}
      volumes:
        - name: fhir-properties
          secret:
            secretName: {{ .Release.Name }}-secret
        - name: fhir-client-truststore
          secret:
            secretName: fhir-client-truststore
      containers:
        - name: {{ template "name" . }}
          image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
          imagePullPolicy: {{ .Values.image.pullPolicy }}
          volumeMounts:
            - name: fhir-properties
              mountPath: /fhir.properties
              subPath: fhir.properties
            - name: fhir-client-truststore
              mountPath: /fhirClientTrustStore.p12
              subPath: fhirClientTrustStore.p12
          args: [
            "--no-scan",
            "--fhir-properties", "/fhir.properties",
            "--tenant-name", "{{ .Values.tenant.id }}",
            "--reindex-tstamp", "{{ .Values.reindex.tstamp }}",
            "--reindex-resource-count", "50",
            "--reindex-concurrent-requests", "{{ .Values.reindex.maxConcurrentRequests }}",
            "--reindex-client-side-driven",
            "--reindex-start-with-index-id", "{{ .Values.reindex.startId }}"
          ]
  backoffLimit: 4

Because the image is so thin, its necessary to mount fhir properties and a truststore in order to invoke reindex.
We should consider either documenting this or providing a helm chart to make this easier...maybe we just extend https://artifacthub.io/packages/helm/alvearie/ibm-fhir-server with a flag for doing reindex?

[prb112]

Updated https://hub.docker.com/r/ibmcom/ibm-fhir-bucket-tool - let me know if you want more.

[prb112]

Chat on the Side agreed it is a good start, will update going forward