PUT /v1/apps/{}/machines/{}/metadata → endpoint removal
Fly.io Machines API
Deprecated, no date
Fly.io deprecated the PUT /v1/apps/{}/machines/{}/metadata endpoint without announcing a shutdown date. Calls made to this route are marked for removal and will eventually fail. The provider notes that the operation is identical to the PATCH method on the same path.
Calls it hits
PUT /v1/apps/{}/machines/{}/metadata
What to use instead of these calls
Send PATCH /v1/apps/{app_name}/machines/{machine_id}/metadata with the same body instead.
In Fly.io Machines API's words
Deprecated: use `PATCH` on the same path, which this is identical to.
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 PUT /v1/apps/{}/machines/{}/metadata 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
-
No date
GET /v1/apps/{}/machines/{}/waitEndpoint 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.