Uploaded image for project: 'OpenShift Hive'
  1. OpenShift Hive
  2. HIVE-2944

Revendor installer past AWS SDK v2 migration

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • None
    • None

      I wish I had a better way of ensuring this card is seen by whoever does the next installer revendor.

      With their v2 migration, the installer side changed where/how they construct and store AWS service clients for destroy. If HIVE-2302 has landed, and we still have the granny switch in place that triggers the old destroy code path, and we do this revendor, we will need to do something to fix that legacy destroy path; else it will result in nil pointer panics as discussed here.

      See also HIVE-2940.

      That is all.

              Unassigned Unassigned
              efried.openshift Eric Fried
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: