In the cloudfront IP range update notifications, we have seen changes that include only IPv6 changes without IPv4 changes. This results in noise in the production slack channel until we apply the changes to the current json file (ref: https://github.com/cssat/ip-ranges#apply-the-update) When there is no IPv4 change, there is nothing to do in aptible as the IP allowlist only includes IPv4. We can reduce the noise by modifying the logic in the handler by removing the ipv6 elements from the returned object from compute_diff function.
In the cloudfront IP range update notifications, we have seen changes that include only IPv6 changes without IPv4 changes. This results in noise in the production slack channel until we apply the changes to the current json file (ref: https://github.com/cssat/ip-ranges#apply-the-update) When there is no IPv4 change, there is nothing to do in aptible as the IP allowlist only includes IPv4. We can reduce the noise by modifying the logic in the handler by removing the ipv6 elements from the returned object from compute_diff function.