Skip to content

Releases: terraform-modules/aws-dynamic-route53

2.0.6

08 Aug 11:57
Compare
Choose a tag to compare
  • 2.0.6 -- 2025-08-08
    • fix exceptions to use the instance of the route53 client object

2.0.5

03 Jan 17:41
Compare
Choose a tag to compare
  • 2.0.5 -- 2025-01-03
    • change inline role policy to aws_iam_role_policy

add context and event id to sns message; add output on mismatch heritage

17 May 13:24
Compare
Choose a tag to compare
  • 2.0.4 -- 2023-05-17
    • code 2.0.4
      • add context info and event id to SNS messages
      • add heritage mismatch information to output

fix emr cluster detection

11 May 17:31
Compare
Choose a tag to compare
  • 2.0.3 -- 2023-05-11
    • code 2.0.3
      • fix emr cluster detection

added pagination to get zones by vpc

29 Apr 18:50
Compare
Choose a tag to compare
  • 2.0.1 -- 2023-04-29
    • code 2.0.1
      • add pagination for list hosted zone by vpc (as some vpcs have hundreds of zones, specifically the one with dns endpoints)

refactor: flags, cleans up properly, emr capability

28 Apr 21:35
Compare
Choose a tag to compare
  • 2.0.0 -- 2023-04-28
    • code 2.0.0
      • use sessions
      • make assume role call to remote account where PHZ is defined
      • add dns entries to the DDB item, so that on stop/terminate we delete only what was added
      • add flags: noforward, noptr, noheritage, nocname
      • add data: boc:dns:ptrname
      • add detection of a runnign EMR cluster with aws:elasticmapreduce: job-flow-id (cluster) and instance-group-role and use this to
        set an alias defined in boc:dns:cname ({friendlyname}.master), but if it is a cluser node, only use the cname if it is master. If
        it is not a cluster, set the cname

change map() to {}

28 Oct 21:45
Compare
Choose a tag to compare
  • 1.0.1 -- 2022-10-28
    • change map() to {}

release

27 Apr 12:34
Compare
Choose a tag to compare

Release 1.x

  • 1.0.0 -- 2022-04-27
    • release code as ready to be deployed in accounts and regions

change version to test heritage code

26 Apr 20:10
Compare
Choose a tag to compare
  • 0.3.1 - 2022-04-26
    • change version purely to test heritage code handling a version change

code 0.3.0, cleanup of deletes, heritage verification

18 Apr 20:45
Compare
Choose a tag to compare
  • 0.3.0 -- 2022-04-18
  1. created a new def process_delete_record function to combine "repeating" tasks between A, PTR, and CNAME process. The code was combined with what was there before. Instead of doing the same process over 3 times, I just created a function and call it 3 times.
  2. The def process_delete_record function performs:
    1. checks TXT heritage validation (do I own it? does the instance ID match?)
    2. Also sends SNS notification if heritage validation fails.
    3. If not not pass validation, it skips deletion and sns notify
    4. If so, it deletes the records - (A, PTR, or CNAME and associated TXT)
  3. Fixed LOGGER.info lines that had a typo (missing parameter) in the sns notification caller. Example line 2274 but several others.
  4. Fixed lOGGER.info to convert MAX_API_RETRY to string when writing to log. Example line 2264 but several others.
  5. Updated new_get_resource_record with several fixes.
    1. Return "" instead of Non if not found -- better align with parent function that calls it.
    2. Checks the value of the list_resource_record_sets to match what should be returned. This is because the list_resource_record_sets API returns the next record (instead of matching exact) so wrong record can be retrieved if we do not check it.
    3. MaxItem value changed to string.
  6. Fixed def parse_heritage to add more logging and better input validation
  7. Fixed def get_heritage_item to check input type and add more logging