Datadog API
/api/v1/integration/gcp endpoint removal
Deprecated, no dateSubscribe to Datadog APIShare
Datadog API deprecated the /api/v1/integration/gcp endpoint without a shutdown date. Calls made to this route are marked for removal and will eventually fail. The documentation advises clients to use the V2 endpoints instead.
Calls it hits
/api/v1/integration/gcp
What to use instead of these calls
Manage GCP service accounts with /api/v2/integration/gcp/accounts and /api/v2/integration/gcp/accounts/{account_id}.
In Datadog API's words
This endpoint is deprecated – use the V2 endpoints instead.
Facts
- API
- Datadog API
api.datadoghq.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Datadog API's own pages
Questions
When does this change take effect?
Datadog API deprecated /api/v1/integration/gcp without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Datadog API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Datadog API 8
-
No date
/api/v1/downtime*Endpoint removal Deprecated, no date -
No date
/api/v1/integration/awsEndpoint removal Deprecated, no date -
No date
/api/v2/metrics/config/bulk-tagsEndpoint removal Deprecated, no date -
No date
GET /api/v1/searchEndpoint removal Deprecated, no date -
No date
GET /api/v1/usage/hostsEndpoint removal Deprecated, no date -
No date
GET /api/v1/usage/logsEndpoint removal Deprecated, no date -
No date
GET /api/v1/usage/timeseriesEndpoint removal Deprecated, no date -
No date
POST /api/v2/dora/incidentEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.