Uploaded image for project: 'Ansible Cloud Automation'
  1. Ansible Cloud Automation
  2. ACA-1998

Terminator should delete in multiple regions

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • cloud-content
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      • The playbook to deploy the terminator sets an env var with a list of regions to run across
      • Terminator lambda accepts an env var containing a list of regions to run across
      • Terminator lambda deletes resources across multiple regions
      Show
      The playbook to deploy the terminator sets an env var with a list of regions to run across Terminator lambda accepts an env var containing a list of regions to run across Terminator lambda deletes resources across multiple regions
    • Cloud Content Sprint 45

      Background

      The terminator lambda for the content account currently only runs against a single region. That region is configurable, but given that we have resources spread out potentially across 17 regions, that would mean 17 different lambdas. The volume of resources we create is relatively small, so it should be reasonable for a single lambda to manage several regions.

      Update the lambda to be able to delete resources in multiple regions. The lambda should read an env var that contains a list of regions to run across. For now, we can plan on three different lambdas (NA, EU, APAC).

      IMPORTANT Make sure you are using the content terminator (https://github.com/ansible/aws-ci-admin) not the aws-termintor that's used for our collection testing.

      Definition of Done

      • All tests pass
      • Documentation has been updated

              abikouo1@redhat.com BIKOUO AUBIN
              mgraves1@redhat.com Mike Graves
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: