Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-2433

References to orchestrator-helm-chart repo must be updated

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Description of the problem:
      In various places referring to the postgresql installation, we refer to the orchestrator-helm chart repo, for example:

      git clone git@github.com:rhdhorchestrator/orchestrator-helm-chart.git

      This should be updated to refer to the orchestrator-go-operator repo. The values.yaml for the postgresql chart should be copied to the new location.

       
      There shouldn't be any reference from the ochestrator-go-operator to any of the previous repos.
       
      This should be fixed in the following places:

      ~/dev/orchestrator/orchestrator-go-operator  main                                                                                                                                                                              
╰─ git grep 'orchestrator-helm-chart'
docs/main/README.md:      the [PostgreSQL values](https://github.com/rhdhorchestrator/orchestrator-helm-chart/blob/main/postgresql/values.yaml)
docs/postgresql/README.md:git clone git@github.com:rhdhorchestrator/orchestrator-helm-chart.git
docs/postgresql/README.md:cd orchestrator-helm-chart/postgresql
docs/postgresql/README.md:Note: the default settings provided in [PostgreSQL values](https://github.com/rhdhorchestrator/orchestrator-helm-chart/blob/main/postgresql/values.yaml) match the defaults provided in the
docs/release-1.5/README.md:      the [PostgreSQL values](https://github.com/rhdhorchestrator/orchestrator-helm-chart/blob/main/postgresql/values.yaml)
internal/controller/rhdh/rhdh_config_catalog.go:      target: https://github.com/rhdhorchestrator/orchestrator-helm-chart/blob/main/resources/users.yaml

      Expected results: See above

              jubah@redhat.com Jennifer Ubah
              yfirst Yona First
              Yona First Yona First
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: