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

Running Jira on Docker sets schema-name=public for all DB types

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • None
    • master
    • Environment - Docker
    • None
    • Severity 2 - Major

      Issue Summary

      In our Jira Docker images, the dbconfig.xml.j2 template contains a hard-coded schema name:

      <schema-name>public</schema-name>
      

      This breaks other DB's, notably MSSQL.

      Steps to Reproduce

      Start Docker image with ATL_DB/JDBC_* values specified for MSSQL

      Expected Results

      A valid dbconfig.xml should be generated for MSSQL

      Actual Results

      schema-name is set to "public", which isn't necessarily valid.

      Workaround

      N/A

            [SCALE-6] Running Jira on Docker sets schema-name=public for all DB types

            This has been fixed and published for all publicly available versions on Docker Hub. Simply re-pull whichever tag you're using to get the fixed version.

            Dave Chevell added a comment - This has been fixed and published for all publicly available versions on Docker Hub. Simply re-pull whichever tag you're using to get the fixed version.

            This change (plus a bit of documentation in the README) will enable use of MSSQL

            dbconfig.xml.j2
            6c6
            <   <schema-name>public</schema-name>
            ---
            >   <schema-name>{{ atl_jdbc_schema | default('public') }}</schema-name>
            
            

            chrisruscio added a comment - This change (plus a bit of documentation in the README) will enable use of MSSQL dbconfig.xml.j2 6c6 < <schema-name>public</schema-name> --- > <schema-name>{{ atl_jdbc_schema | default('public') }}</schema-name>

              dchevell Dave Chevell
              dchevell Dave Chevell
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: