API changelog for release 4.74.0 #259
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| --- | ||
| title: '4.74.0: 2020-09-08' | ||
| date: 2020-09-08T04:00:00.000Z | ||
| version: 4.74.0 | ||
| changelog: | ||
| - API | ||
| --- | ||
|
|
||
| ### Added | ||
|
|
||
| * Added the *Reset Linode Root Password* ([POST /linode/instances/{linodeId}/password](/api/v4/linode-instances-linode-id-password/#post)) endpoint to the *Linode Instances* collection. Use this endpoint to reset the root password for a Linode. | ||
|
|
||
| * Added the `bucket_access` field to the *Create an Object Storage Key* ([POST /object-storage/keys](/api/v4/object-storage-keys/#post)) endpoint. This field defines an Object Storage key as a *Limited Access Key*. Limited Access Keys have access to only the bucket(s) that are specified along with `read_write` or `read_only` bucket-level permissions. Limited Access Keys can: | ||
|
Collaborator
There was a problem hiding this comment. Should check with Vicki to make sure this is correct. |
||
|
|
||
| * [list all buckets](/api/v4/object-storage-buckets/) available on an Account, but cannot perform any actions on a bucket unless it has access to the bucket. | ||
|
|
||
| * [create new buckets](/api/v4/object-storage-buckets/#post), but do not have any access to the buckets it creates, unless explicitly given access to them. | ||
|
|
||
| * [NodeBalancers](https://www.linode.com/products/nodebalancers/) now support Proxy Protocol with the addition of the `proxy_protocol` field. Proxy Protocol sends TCP client connection information, like source and destination IP addresses and port numbers, to your NodeBalancer's backend nodes. This new field is available in the following NodeBalancer endpoints: | ||
|
|
||
| * List Configs ([GET /nodebalancers/{nodeBalancerId}/configs](/api/v4/nodebalancers-node-balancer-id-configs)) | ||
| * Create Config ([POST /nodebalancers/{nodeBalancerId}/configs](/api/v4/nodebalancers-node-balancer-id-configs/#post)) | ||
| * View Config ([GET /nodebalancers/{nodeBalancerId}/configs/{configId}](/api/v4/nodebalancers-node-balancer-id-configs-config-id)) | ||
| * Update Config ([PUT /nodebalancers/{nodeBalancerId}/configs/{configId}](/api/v4/nodebalancers-node-balancer-id-configs-config-id/#put)) | ||
| * Delete Config ([DELETE /nodebalancers/{nodeBalancerId}/configs/{configId}](/api/v4/nodebalancers-node-balancer-id-configs-config-id/#delete)) | ||
| * Rebuild Config ([POST /nodebalancers/{nodeBalancerId}/configs/{configId}/rebuild](/api/v4/nodebalancers-node-balancer-id-configs-config-id-rebuild/#post)) | ||
|
|
||
| * The [APIv4 OpenAPI 3 reference](https://github.com/linode/linode-api-docs) now correctly documents the `prefix` and `route_target` fields as part of the [List IPv6 Ranges](/api/v4/networking-ipv-6-ranges) endpoint. Previously, these fields were mistakenly left out of the APIv4 OpenAPI 3 reference. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is specifically for Bare Metal instances. I would check with @Dorthu to see if this should be announced.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This endpoint is not specific to bare metal instances
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not the endpoint, the password reset comment itself, which I believe was coming from this line in the changelog: https://bits.linode.com/LinodeAPI/apinext/pull/2910/files#diff-4ac32a78649ca5bdd8e0ba38b7006a1eR14