Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-1705

[EAP7] fix datasource issues

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • EAP7
    • None
    • CLOUD Maintenance Sprint 7

      • validate_legacy_params return 1 kills the pod (use mysql1 as name not mysql). Or use DATASOURCES without XX_SERVICE_HOST, XX_SERVICE_PORT or XX_DATABASE
      • if you add a PG and MYSQL db and there's a problem with the MYSQL config you get duplicate copies of PG which blows up on start for duplicate resources
      • TX datasource is always the 2nd datasource regardless of TX_DATABASE_PREFIX_MAPPING
      • Limited to one instance of each db type

              wdecoste1@redhat.com William Decoste (Inactive)
              wdecoste1@redhat.com William Decoste (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: