Okapi Okapi

GET /v1/apps/{}/machines/{}/wait → endpoint removal

Fly.io Machines API

Deprecated, no date

The Fly.io Machines API deprecated the instance_id query parameter on GET /v1/apps/{}/machines/{}/wait without a shutdown date. The provider notes that the 26-character Machine version ID is deprecated; use version. Affected calls that rely on this parameter will fail once removed.


Calls it hits

  • GET /v1/apps/{}/machines/{}/wait
  • query parameter instance_id

What to use instead of these calls

Send the Machine version ID as version instead of instance_id.

In Fly.io Machines API's words

26-character Machine version ID (deprecated; use version)

Fly.io Machines API, Announcement

Facts

API
Fly.io Machines API api.machines.dev
Kind
Endpoint removal
Takes effect
No date given yet
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Fly.io Machines API's own pages

Questions

When does this change take effect?

Fly.io Machines API deprecated GET /v1/apps/{}/machines/{}/wait, query parameter instance_id without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: Fly.io Machines 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 Fly.io Machines API 1

  1. No date PUT /v1/apps/{}/machines/{}/metadataEndpoint 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.

Add to GitHub