You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, only DNS firewall, Railgun, and ZoneIDByName can depend on the global api.AccountID (possibly via api.userBaseURL). I wonder if it is in the plan to completely stop using the global api.AccountID even outside the Terraform-related API. The current interface is slightly confusing because it is unclear when api.AccountID is used. If it is indeed planned to remove api.AccountID, I hope the field and the setter will soon be deprecated and then removed.
Use cases
A clear indication that api.AccountID will not be used (if that is the plan).
Potential cloudflare-go usage
// This does not address other endpoints related to RailguntypeRailgunListOptionsstruct {
AccountIDstringDirectionstring
}
// This does not address other endpoints related to DNS FirewalltypeDNSFirewallUserAnalyticsOptionsstruct {
AccountIDstringMetrics []stringSince*time.TimeUntil*time.Time
}
References
No response
The text was updated successfully, but these errors were encountered:
Current cloudflare-go version
0.57
Description
Currently, only DNS firewall, Railgun, and
ZoneIDByName
can depend on the globalapi.AccountID
(possibly viaapi.userBaseURL
). I wonder if it is in the plan to completely stop using the globalapi.AccountID
even outside the Terraform-related API. The current interface is slightly confusing because it is unclear whenapi.AccountID
is used. If it is indeed planned to removeapi.AccountID
, I hope the field and the setter will soon be deprecated and then removed.Use cases
A clear indication that
api.AccountID
will not be used (if that is the plan).Potential cloudflare-go usage
References
No response
The text was updated successfully, but these errors were encountered: