Bitrise API
PUT /v0.1/apps/{id}/secrets/{id} endpoint removal
Deprecated, no dateSubscribe to Bitrise APIShare
Bitrise deprecated PUT /v0.1/apps/{id}/secrets/{id} on October 31, 2024, without a shutdown date. Bitrise API listed it among endpoints that are going out, and affected calls will fail once removed.
Calls it hits
PUT /v0.1/apps/{id}/secrets/{id}
What to use instead of these calls
Create secrets with POST /v0.1/apps/{app-slug}/secrets and update them with PATCH /v0.1/apps/{app-slug}/secrets/{secret-name}.
In Bitrise API's words
Deprecated endpoints—what’s going out
Facts
- API
- Bitrise API
api.bitrise.io - Kind
- Endpoint removal
- Announced
- October 31, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Bitrise API's own pages
Questions
When does this change take effect?
Bitrise API deprecated PUT /v0.1/apps/{id}/secrets/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Bitrise 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 Bitrise API 2
-
No date
GET /v0.1/apps/{id}/secrets/{id}/valueEndpoint removal Deprecated, no date -
No date
/release-management/v1/*Version retirement 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.