Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-10924

keep only a single set of porta configuration files

XMLWordPrintable

    • False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      🐚 ls openshift/system/config/
      amazon_s3.yml      core.yml        oauth2.yml      rolling_updates.yml    settings.yml          web_hooks.yml
      backend_redis.yml  cors.yml        paperclip.yml   sandbox_proxy.yml      sidekiq_schedule.yml
      backend.yml        currencies.yml  prometheus.yml  segment.yml            smtp.yml
      cache_store.yml    database.yml    redis.yml       service_discovery.yml  unicorn.rb
      

      There is no need for separate configuration files inside openshift/system/config/ and config/(examples) because all deployments use the ones in the openshift folder.

      Ideally we also get rid of most customizations done in SaaS deployment.

      Any differences in these compared to the ones in config/ and config/examples should be resolved in favor of these inside the openshift folder while retaining the configuration for "development" and "test" environments in the ones inside config/

      Presently it is a nuisance to keep two versions and there is a possiblity to update one of the versions and forget the other. Will be much more straightforward to have one.

            rhn-support-dmayorov Daria Mayorova
            akostadi1@redhat.com Aleksandar Kostadinov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: