Closed mohith10 closed 9 months ago
Note: The getExternalDNSRecord call doesn't contain 'dns asset' information in the response, contrary to what is expected. Resulting in a 400 Bad Request when the 'dns asset id' is sent in the POST request. Eduardo Lemes is working this issue. So this is being sidelined for this PR and will be fixed in the future.
Can you explain this a little more, is the feature broken until the future fix?
Note: The getExternalDNSRecord call doesn't contain 'dns asset' information in the response, contrary to what is expected. Resulting in a 400 Bad Request when the 'dns asset id' is sent in the POST request. Eduardo Lemes is working this issue. So this is being sidelined for this PR and will be fixed in the future.
Can you explain this a little more, is the feature broken until the future fix?
I suspect it as an issue on the API server side.
So when I am adding the dnsAssets info in my request, it is throwing "Forbidden" error.
Also if i make GET request to fetch the external DNS Assets, the dnsAsset field isn't there.
Description
This pull request integrates the External DNS feature into the product. The following things will be introduced in the PR:
Note: The getExternalDNSRecord call doesn't contain 'dns asset' information in the response, contrary to what is expected. Resulting in a 400 Bad Request when the 'dns asset id' is sent in the POST request. Eduardo Lemes is working this issue. So this is being sidelined for this PR and will be fixed in the future.
Type of Change
Checklist