Uploaded image for project: 'Server Deployments and Scale'
  1. Server Deployments and Scale
  2. SCALE-152

Database Switching with Ansible Flag doesn't switch DB changes to new DB

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • AWS Quick Start
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      In the event of Disaster Recovery, a replica RDS will be promoted.

      The database in the CF template can then be switched by using the ansible flag in "Ansible Commands":
      -e atl_db_host=<RDS Endpoint>

      However, once you've switched to the newly Promoted DB, the CF template will not recognize that change and any changes to the DB instance, size for example, will modify the original DB that was created and not the new DB you've switched to.

      Is there a modification in the template we can use for it to recognise the Ansible flag and modify the DB Endpoint that's been stated in "-e atl_db_host=" ?

      If you delete the database the template become defunct, and you can no longer manage anything. Understanding the CF templates are no longer supported so I'm hoping someone from the community could assist if not Atlassian themselves.

            [SCALE-152] Database Switching with Ansible Flag doesn't switch DB changes to new DB

            Yevhen made changes -
            Status Original: Gathering Interest [ 11772 ] New: Not Being Considered [ 11776 ]
            Chris Surman created issue -

              Unassigned Unassigned
              ef18dca6d99f Chris Surman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: