-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
report relevant zone records in DNS Record status #205
Comments
maksymvavilov
added a commit
that referenced
this issue
Sep 19, 2024
Signed-off-by: Maskym Vavilov <[email protected]>
maksymvavilov
added a commit
that referenced
this issue
Sep 19, 2024
Signed-off-by: Maskym Vavilov <[email protected]>
maksymvavilov
added a commit
that referenced
this issue
Sep 26, 2024
Signed-off-by: Maskym Vavilov <[email protected]>
maksymvavilov
added a commit
that referenced
this issue
Sep 26, 2024
Signed-off-by: Maskym Vavilov <[email protected]>
maksymvavilov
added a commit
that referenced
this issue
Oct 7, 2024
Signed-off-by: Maskym Vavilov <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 18, 2024
Add related endpoints to DNSRecord status
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Get all records from the root domain of this DNS Record down to the leaf records (for all owner IDs), and report them (along with owner IDs) in the status of the DNS Record.
In the same format as proposed in #204
Build this from the data pulled from the provider during reconcile if possible, and avoid making a new request to the DNS Provider API.
Add tests to validate the status is updated correctly.
The text was updated successfully, but these errors were encountered: