GoDaddy API EOL note

Author: Alexey Vekshin

README.md

@@ -4,6 +4,10 @@ This plug-in enables the management of individual DNS resource records for domai
 
 It only manages DNS (no e.g. domain management) and aims to manage individual DNS resource records (not the whole domain), while preserving existent records and tolerating external modifications.
 
+## GoDaddy API access restrictions
+
+Unfortunately, at the start of May 2024 GoDaddy suddenly decided to restrict access to their DNS management API. There were no announcements of this policy change and as of 2024.05.08 it is still not reflected in [developers' documentation](https://developer.godaddy.com/getstarted), but there are [many](https://www.reddit.com/r/godaddy/comments/1chs1j8/godaddy_access_denied_via_apicall/) [reports](https://www.reddit.com/r/godaddy/comments/1bl0f5r/am_i_the_only_one_who_cant_use_the_api/) of the same [problem](https://community.letsencrypt.org/t/getting-unauthorized-url-error-while-trying-to-get-cert-for-subdomains/217329) (i.e. getting an "Authenticated user is not allowed access" error while accessing DNS API with the valid keys). So for now the development of this provider is stopped.
+
 ## Usage
 
 Example usage (set credentials in `GODADDY_API_KEY` and `GODADDY_API_SECRET` env vars):
@@ -46,4 +50,4 @@ Differences vs n3integration provider and its forks:
 - configuration object is record, not (top-level) domain no need to bring it all under terraform management
 - could safely manage a subset of records (e.g. only one TXT or CNAME at domain top), keeping the rest intact
 - updates do not result in scary plans threatening to destroy all the records in the whole domain
-- `destroy` is fully supported and removes only previously created records
+- `destroy` is fully supported and removes only previously created records