Uploaded image for project: 'Server Deployments and Scale'
  1. Server Deployments and Scale
  2. SCALE-122

Document how to pass Bitbucket properties

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • None
    • Documentation, Kubernetes
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Current behaviour

      There is no documentation on how to pass the following properties to the deployment:

      Since we are using the Docker image from the bitbucket-server under the hood, the properties will be passed via Environment Variables. This will be the same for the Helm chart:

      Note:

      • This can be achieved by the following:
        • For Bitbucket properties:
          bitbucket:
            [...]
            additionalEnvironmentVariables:
            - name: SEACRH_ENABLED
              value: false
            - name: PLUGIN_SEARCH_CONFIG_BASEURL
              value: http://my.opensearch.host
          
        • For Mesh properties:
          bitbucket:
            [...]
            mesh:
              [...]
              additionalEnvironmentVariables:
              - name: GIT_PATH_EXECUTABLE
                value: /usr/bin/git
          
      • To translate property into an environment variable:
        • dot . becomes underscore _
        • dash - becomes underscore _
        • Example: my.new-property becomes MY_NEW_PROPERTY

      Suggested solution:

      Attachments

        Activity

          People

            Unassigned Unassigned
            mmuthusamy Moga
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: