diff --git a/.gitignore b/.gitignore index 5514598..8a9c903 100644 --- a/.gitignore +++ b/.gitignore @@ -6,3 +6,4 @@ /linode-cli-5.17.1.tar.gz /linode-cli-5.23.0.tar.gz /v5.28.1.tar.gz +/v5.35.0.tar.gz diff --git a/linode-cli.spec b/linode-cli.spec index 53a7896..29fcb4d 100644 --- a/linode-cli.spec +++ b/linode-cli.spec @@ -1,5 +1,5 @@ Name: linode-cli -Version: 5.28.1 +Version: 5.35.0 Release: %autorelease Summary: Official command-line interface to the Linode platform @@ -44,6 +44,8 @@ mv data-3 %{buildroot}/%{python3_sitelib}/linodecli/ %files -f %{pyproject_files} %doc README.rst %license LICENSE +%{_bindir}/lin +%{_bindir}/linode %{_bindir}/linode-cli %{_datadir}/bash-completion/ %{python3_sitelib}/linodecli/data-3 diff --git a/openapi.yaml b/openapi.yaml index d202844..5ff585b 100644 --- a/openapi.yaml +++ b/openapi.yaml @@ -1,6 +1,6 @@ openapi: 3.0.1 info: - version: 4.142.2 + version: 4.150.0 title: Linode API description: | @@ -39,16 +39,17 @@ info: Linode Cloud Manager or the [Create Personal Access Token](/docs/api/profile/#personal-access-token-create) endpoint. - All scopes for the OAuth security model ([defined below](/docs/api/profile/#oauth)) apply to this + All scopes for the OAuth security model ([defined below](/docs/api/#oauth)) apply to this security model as well. - #### Authentication + ### Authentication | Security Scheme Type: | HTTP | |-----------------------|------| | **HTTP Authorization Scheme** | bearer | - ### OAuth + ## OAuth + If you only need to access the Linode API for personal use, we recommend that you create a [personal access token](/docs/api/#personal-access-token). If you're designing an application that can authenticate with an arbitrary Linode user, then @@ -65,7 +66,7 @@ info: - A public client is used with applications where the client secret is not guaranteed to be secure. For example, a native app running on a user's computer may not be able to keep the client secret safe, as a user could potentially inspect the source of the application. So, native apps or apps that run in a user's browser should use a public client. - Public and private clients follow different workflows, as described below. - #### OAuth Workflow + ### OAuth Workflow The OAuth workflow is a series of exchanges between your third-party app and Linode. The workflow is used to authenticate a user before an application can start making API calls on the user's behalf. @@ -137,30 +138,34 @@ info: You'll get another response with an updated `access_token` and `refresh_token`, which can then be used to refresh access again. - #### OAuth Reference + ### OAuth Reference | Security Scheme Type | OAuth 2.0 | |-----------------------|--------| - | **Authorization URL** | https://login.linode.com/oauth/authorize | - | **Token URL** | https://login.linode.com/oauth/token | + | **Authorization URL** | `https://login.linode.com/oauth/authorize` | + | **Token URL** | `https://login.linode.com/oauth/token` | | **Scopes** |
| ## Requests - Requests must be made over HTTPS to ensure transactions are encrypted. The - following Request methods are supported: + Requests must be made over HTTPS to ensure transactions are encrypted. Data included in requests must be supplied in json format unless otherwise specified in the command description. - | METHOD | USAGE | - |--------|-------| - | GET | Retrieves data about collections and individual resources. | - | POST | For collections, creates a new resource of that type. Also used to perform actions on action endpoints. | - | PUT | Updates an existing resource. | - | DELETE | Deletes a resource. This is a destructive action. | + The following request methods are supported: + | METHOD | USAGE | + |---------|-------| + | GET | Retrieves data about collections and individual resources. | + | POST | For collections, creates a new resource of that type. Also used to perform actions on action endpoints. | + | PUT | Updates an existing resource. | + | DELETE | Deletes a resource. This is a destructive action. | + | HEAD | Returns only the response header information of a GET request | + | OPTIONS | Provides permitted communication options for a command | ## Responses - Actions will return one following HTTP response status codes: + ### Response Status Codes + + Actions will return one of the following HTTP response status codes: | STATUS | DESCRIPTION | |---------|-------------| @@ -175,6 +180,38 @@ info: | 429 Too Many Requests | You've hit a rate limit. | | 500 Internal Server Error | Please [open a Support Ticket](/docs/api/support/#support-ticket-open). | + ### Response Headers + + There are many ways to access response header information for individual command URLs, depending on how you are accessing the Linode API. For example, to view HTTP response headers for the `/regions` endpoint when making requests with `curl`, use the `-I` or `--head` option as follows: + + ```Shell + curl -I https://api.linode.com/v4/regions + ``` + + Responses may include the following headers: + + | HEADER | DESCRIPTION | EXAMPLE | + |--------|-------------|---------| + | Access-Control-Allow-Credentials | Responses to credentialed requests are exposed to frontend JavaScript code. | true | + | Access-Control-Allow-Headers | All permissible request headers for this endpoint. | Authorization, Origin, X-Requested-With, Content-Type, Accept, X-Filter | + | Access-Control-Allow-Methods | Permissible HTTP methods for this endpoint | HEAD, GET, OPTIONS, POST, PUT, DELETE | + | Access-Control-Allow-Origin | Indicates origin access permissions. The wildcard character `*` means any origin can access the resource. | * | + | Access-Control-Expose-Headers | Available headers to include in response to cross-origin requests. | X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Status | + | Cache-Control | Controls caching in browsers and shared caches such as CDNs. | private, max-age=60, s-maxage=60 | + | Content-Security-Policy | Controls which resources are allowed to load. By default, resources do not load. | default-src 'none' | + | Content-Type | All responses are in json format. | application/json | + | Content-Warning | A message containing instructions for successful requests that were not able to be completed. | Please contact support for assistance. | + | Retry-After | The remaining time in seconds until the current [rate limit](#rate-limiting) window resets. | 60 | + | Strict-Transport-Security | Enforces HTTPS-only access until the returned time in seconds. | max-age=31536000 | + | Vary | Optional request headers that affected the response content. | Authorization, X-Filter | + | X-Accepted-OAuth-Scopes | Required [scopes](#oauth-reference) for accessing the requested command. | linodes:read_only | + | X-Customer-UUID | A unique identifier for the account owning the the [personal access token](#personal-access-token) that was used for the request. | ABCDEF01-3456-789A-BCDEF0123456789A | + | X-OAuth-Scopes | Allowed [scopes](#oauth-reference) associated with the [personal access token](#personal-access-token) that was used for the request. A value of `*` indicates read/write access for all scope categories. | images:read_write linodes:read_only | + | X-RateLimit-Limit | The maximum number of permitted requests during the [rate limit](#rate-limiting) window for this endpoint. | 800 | + | X-RateLimit-Remaining | The remaining number of permitted requests in the current [rate limit](#rate-limiting) window. | 798 | + | X-RateLimit-Reset | The time when the current [rate limit](#rate-limiting) window rests in UTC epoch seconds. | 1674747739 | + | X-Spec-Version | The current API version that handled the request. | 4.150.0 | + ## Errors Success is indicated via Standard HTTP status codes. @@ -193,7 +230,6 @@ info: new errors coming back once we are able to get further along in the process of handling your request. - Within each error object, the `field` parameter will be included if the error pertains to a specific field in the JSON you've submitted. This will be omitted if there is no relevant field. The `reason` is a human-readable @@ -363,19 +399,13 @@ info: ### Rate Limit HTTP Response Headers - The Linode API includes the following HTTP response headers which are designed to help you avoid hitting rate limits that might disrupt your applications: + The Linode API includes the following HTTP response headers which are designed to help you avoid hitting rate limits which might disrupt your applications: * **X-RateLimit-Limit**: The maximum number of permitted requests during the rate limit window for this endpoint. * **X-RateLimit-Remaining**: The remaining number of permitted requests in the current rate limit window. * **X-RateLimit-Reset**: The time when the current rate limit window rests in UTC epoch seconds. * **Retry-After**: The remaining time in seconds until the current rate limit window resets. - There are many ways to access header information for your requests, depending on how you are accessing the Linode API. For example, to view HTTP response headers when making requests with `curl`, use the `-i` or `--include` option as follows: - - ```Shell - curl -i https://api.linode.com/v4/regions - ``` - ## CLI (Command Line Interface) The Linode CLI allows you to easily @@ -6029,7 +6059,7 @@ paths: type: string pattern: \A(\*\.)?([a-zA-Z0-9-_]{1,63}\.)+([a-zA-Z]{2,3}\.)?([a-zA-Z]{2,16}|xn--[a-zA-Z0-9]+)\Z minLength: 1 - maxLength: 255 + maxLength: 253 description: > The new domain for the clone. Domain labels cannot be longer than 63 characters and must conform to [RFC1035](https://tools.ietf.org/html/rfc1035). @@ -6120,8 +6150,10 @@ paths: - oauth: - domains:read_write summary: Domain Record Create - description: > + description: | Adds a new Domain Record to the zonefile this Domain represents. + + Each domain can have up to 12,000 active records. operationId: createDomainRecord x-linode-cli-action: records-create requestBody: @@ -10155,7 +10187,7 @@ paths: -X POST -d '{ "label": "cluster12345", "region": "us-central", - "k8s_version": "1.24", + "k8s_version": "1.25", "tags": ["ecomm", "blogs"], "control_plane": { "high_availability": true @@ -10182,7 +10214,7 @@ paths: linode-cli lke cluster-create \ --label cluster12345 \ --region us-central \ - --k8s_version 1.24 \ + --k8s_version 1.25 \ --control_plane.high_availability true \ --node_pools.type g6-standard-4 --node_pools.count 6 \ --node_pools.type g6-standard-8 --node_pools.count 3 \ @@ -10342,7 +10374,7 @@ paths: linode-cli lke cluster-update 12345 \ --label lkecluster54321 \ --control_plane.high_availability true \ - --k8s_version 1.24 \ + --k8s_version 1.25 \ --tags ecomm \ --tags blog \ --tags prod \ @@ -11069,6 +11101,116 @@ paths: - lang: CLI source: > linode-cli lke kubeconfig-delete 12345 + /lke/clusters/{clusterId}/regenerate: + parameters: + - name: clusterId + in: path + description: ID of the target Kubernetes cluster. + required: true + schema: + type: integer + x-linode-cli-command: lke + post: + operationId: postLKEClusterRegenerate + x-linode-cli-action: regenerate + security: + - personalAccessToken: [] + - oauth: + - lke:read_write + tags: + - Linode Kubernetes Engine (LKE) + summary: Kubernetes Cluster Regenerate + description: | + Regenerate the Kubeconfig file and/or the service account token for a Cluster. + + This is a helper command that allows performing both the [Kubeconfig Delete](#kubeconfig-delete) and the [Service Token Delete](#service-token-delete) actions with a single request. + + When using this command, at least one of `kubeconfig` or `servicetoken` is required. + + **Note**: When regenerating a service account token, the Cluster's control plane components and Linode CSI drivers are also restarted and configured with the new token. High Availability Clusters should not experience any disruption, while standard Clusters may experience brief control plane downtime while components are restarted. + requestBody: + description: The Kubernetes Cluster Regenerate request object. + content: + application/json: + schema: + properties: + kubeconfig: + type: boolean + default: false + example: true + description: | + Whether to delete and regenerate the Kubeconfig file for this Cluster. + servicetoken: + type: boolean + default: false + example: true + description: | + Whether to delete and regenerate the service access token for this Cluster. + responses: + '200': + description: Regenerate request successful. + content: + application/json: + schema: + type: object + default: + $ref: '#/components/responses/ErrorResponse' + x-code-samples: + - lang: Shell + source: > + curl -H "Content-Type: application/json" \ + -H "Authorization: Bearer $TOKEN" \ + -X POST -d '{ + "kubeconfig": true; + "servicetoken": true + }' \ + https://api.linode.com/v4/lke/clusters/12345/regenerate + - lang: CLI + source: > + linode-cli lke regenerate 12345 \ + --kubeconfig true \ + --servicetoken true + /lke/clusters/{clusterId}/servicetoken: + parameters: + - name: clusterId + in: path + description: ID of the target Kubernetes cluster. + required: true + schema: + type: integer + x-linode-cli-command: lke + delete: + operationId: postLKECServiceTokenDelete + x-linode-cli-action: service-token-delete + security: + - personalAccessToken: [] + - oauth: + - lke:read_write + tags: + - Linode Kubernetes Engine (LKE) + summary: Service Token Delete + description: | + Delete and regenerate the service account token for a Cluster. + + **Note**: When regenerating a service account token, the Cluster's control plane components and Linode CSI drivers are also restarted and configured with the new token. High Availability Clusters should not experience any disruption, while standard Clusters may experience brief control plane downtime while components are restarted. + responses: + '200': + description: Service token deleted and regenerated successfully. + content: + application/json: + schema: + type: object + default: + $ref: '#/components/responses/ErrorResponse' + x-code-samples: + - lang: Shell + source: > + curl -H "Authorization: Bearer $TOKEN" \ + -X DELETE \ + https://api.linode.com/v4/lke/clusters/12345/servicetoken + - lang: CLI + source: > + linode-cli lke service-token-delete 12345 /lke/versions: x-linode-cli-command: lke get: @@ -11153,10 +11295,10 @@ paths: - lang: Shell source: > curl -H "Authorization: Bearer $TOKEN" \ - https://api.linode.com/v4/lke/versions/1.24 + https://api.linode.com/v4/lke/versions/1.25 - lang: CLI source: > - linode-cli lke version-view 1.24 + linode-cli lke version-view 1.25 /longview/clients: x-linode-cli-command: longview get: @@ -13053,7 +13195,6 @@ paths: x-linode-cli-command: networking post: servers: - - url: https://api.linode.com/v4 - url: https://api.linode.com/v4beta x-linode-grant: read_write tags: @@ -13100,7 +13241,7 @@ paths: "2001:db8:3c4d:15::" ] }' \ - https://api.linode.com/v4/networking/ips/share + https://api.linode.com/v4beta/networking/ips/share - lang: CLI source: > linode-cli networking ip-share \ @@ -14274,7 +14415,7 @@ paths: https://api.linode.com/v4beta/networking/vlans/ - lang: CLI source: > - linode-cli networking vlans-list + linode-cli vlans list /nodebalancers: x-linode-cli-command: nodebalancers get: @@ -15140,7 +15281,7 @@ paths: https://api.linode.com/v4/nodebalancers/12345/configs/4567/nodes - lang: CLI source: > - linode-cli nodebalancers node-create \ + linode-cli nodebalancers node-update \ 12345 4567 \ --address 192.168.210.120:80 \ --label node54321 \ @@ -16230,23 +16371,23 @@ paths: - lang: Shell source: > curl -H "Content-Type: application/json" \ - -H "Authorization: Bearer $TOKEN" \ - -X POST -d '{ - "label": "my-object-storage-key", - "bucket_access": [ - { - "cluster": "ap-south-1", - "bucket_name": "bucket-example-1", - "permissions": "read_write" - }, - { - "cluster": "us-east-1", - "bucket_name": "bucket-example-2", - "permissions": "read_only" - } - ] - }' \ - https://api.linode.com/v4/object-storage/keys + -H "Authorization: Bearer $TOKEN" \ + -X POST -d '{ + "label": "my-object-storage-key", + "bucket_access": [ + { + "cluster": "ap-south-1", + "bucket_name": "bucket-example-1", + "permissions": "read_write" + }, + { + "cluster": "us-east-1", + "bucket_name": "bucket-example-2", + "permissions": "read_only" + } + ] + }' \ + https://api.linode.com/v4/object-storage/keys - lang: CLI source: > linode-cli object-storage keys-create \ @@ -17049,11 +17190,14 @@ paths: scopes: type: string format: oauth-scope - description: > - The scopes to create the token with. These cannot be changed - after creation, and may not exceed the scopes of the acting token. - If omitted, the new token will have the same scopes as the acting - token. + description: | + The access [scopes](/docs/api#oauth-reference) to grant to the created token. These cannot be changed after creation, and may not exceed the scopes of the acting token. + + If omitted or entered with a wildcard character (`*`), the new token will have the same scopes as the acting token. + + Multiple scopes are separated by a space character (` `). + + For example, `linodes:read_write account:read_only`. example: '*' expiry: type: string @@ -19293,7 +19437,7 @@ components: schema: type: integer minimum: 25 - maximum: 100 + maximum: 500 default: 100 links: bootLinode: @@ -20802,7 +20946,7 @@ components: type: string pattern: \A(\*\.)?([a-zA-Z0-9-_]{1,63}\.)+([a-zA-Z]{2,3}\.)?([a-zA-Z]{2,16}|xn--[a-zA-Z0-9]+)\Z minLength: 1 - maxLength: 255 + maxLength: 253 description: > The domain this Domain represents. Domain labels cannot be longer than 63 characters and must conform to [RFC1035](https://tools.ietf.org/html/rfc1035). @@ -20839,7 +20983,7 @@ components: description: type: string minLength: 1 - maxLength: 255 + maxLength: 253 description: | A description for this Domain. This is for display purposes only. example: null @@ -20971,7 +21115,7 @@ components: `A` and `AAAA`: The hostname or FQDN of the Record. - `NS`: The subdomain, if any, to use with the Domain of the Record. + `NS`: The subdomain, if any, to use with the Domain of the Record. Wildcard NS records (`*`) are not supported. `MX`: The mail subdomain. For example, `sub` for the address `user@sub.example.com` under the `example.com` Domain. Must be an empty string (`""`) for a Null MX Record. @@ -21018,7 +21162,7 @@ components: `CAA`: The value. For `issue` or `issuewild` tags, the domain of your certificate issuer. For the `iodef` tag, a contact or submission URL (domain, http, https, or mailto). Requirements depend on the tag for this record: * `issue`: The domain of your certificate issuer. Must be a valid domain. - * `issuewild`: Must begin with `*`. + * `issuewild`: The domain of your wildcard certificate issuer. Must be a valid domain and must not start with an asterisk (`*`). * `iodef`: Must be either (1) a valid domain, (2) a valid domain prepended with `http://` or `https://`, or (3) a valid email address prepended with `mailto:`. `PTR`: Required. See our guide on how to [Configure Your Linode for Reverse DNS @@ -21028,6 +21172,7 @@ components: example: 192.0.2.0 x-linode-filterable: true x-linode-cli-display: 4 + maxLength: 65535 priority: type: integer minimum: 0 @@ -21529,6 +21674,7 @@ components: username: type: string readOnly: true + nullable: true description: > The username of the User who caused the Event. example: exampleUser @@ -21889,51 +22035,49 @@ components: items: $ref: '#/components/schemas/Grant' description: > - The grants this User has pertaining to Linodes on this Account. - There will be one entry per Linode on the Account. + The grants this User has for each Linode that is owned by this Account. + database: + type: array + items: + $ref: '#/components/schemas/Grant' + description: > + The grants this User has for each Database that is owned by this Account. domain: type: array items: $ref: '#/components/schemas/Grant' description: > - The grants this User has pertaining to Domains on this Account. - There will be one entry per Domain on the Account. + The grants this User has for each Domain that is owned by this Account. nodebalancer: type: array items: $ref: '#/components/schemas/Grant' description: > - The grants this User has pertaining to NodeBalancers on this - Account. There will be one entry per NodeBalancer on the Account. + The grants this User has for each NodeBalancer that is owned by this Account. image: type: array items: $ref: '#/components/schemas/Grant' description: > - The grants this User has pertaining to Images on this Account. - There will be one entry per Image on the Account. + The grants this User has for each Image that is owned by this Account. longview: type: array items: $ref: '#/components/schemas/Grant' description: > - The grants this User has pertaining to Longview Clients on this - Account. There will be one entry per Longview Client on the - Account. + The grants this User has for each Longview Client that is owned by this Account. stackscript: type: array items: $ref: '#/components/schemas/Grant' description: > - The grants this User has pertaining to StackScripts on this - Account. There will be one entry per StackScript on the Account. + The grants this User has for each StackScript that is owned by this Account. volume: type: array items: $ref: '#/components/schemas/Grant' description: > - The grants this User has pertaining to Volumes on this Account. - There will be one entry per Volume on the Account. + The grants this User has for each Block Storage Volume that is owned by this Account. Image: type: object description: Image object @@ -22048,16 +22192,18 @@ components: x-linode-cli-display: 7 type: string readOnly: true + x-linode-filterable: true enum: - creating - pending_upload - available description: | - The current status of this Image. Only Images in an "available" status - can be deployed. Images in a "creating" status are being created from - a Linode Disk, and will become "available" shortly. Images in a - "pending_upload" status are waiting for data to be [uploaded](/docs/api/images/#image-upload), - and become "available" after the upload and processing are complete. + The current status of this Image. + + Only Images in an "available" status can be deployed. Images in a "creating" status are being created from a Linode Disk, and will become "available" shortly. Images in a "pending_upload" status are waiting for data to be [uploaded](/docs/api/images/#image-upload), and become "available" after the upload and processing are complete. + + The "+order_by" and "+order" operators are not available for [filtering](/docs/api/#filtering-and-sorting) on this key. + example: available Invoice: type: object description: Account Invoice object @@ -22868,25 +23014,24 @@ components: readOnly: true memory: type: integer - description: > - The amount of RAM, in MB, this Linode has access to. Typically a Linode will - choose to boot with all of its available RAM, but this can be configured in a - Config profile, see the - [/linode/instances/{linodeId}/configs](/docs/api/linode-instances/#configuration-profiles-list) - endpoints and the LinodeConfig object for more information. + description: | + The amount of RAM, in MB, this Linode has access to. + + Typically, a Linode boots with all of its available RAM, but this can be configured in a Config profile. See the [/linode/instances/{linodeId}/configs](/docs/api/linode-instances/#configuration-profiles-list) endpoints and the LinodeConfig object for more information. example: 4096 readOnly: true vcpus: type: integer description: > The number of vcpus this Linode has access to. - Typically a Linode will choose to - boot with all of its available vcpus, but this can be configured in a Config - Profile, see the - [/linode/instances/{linodeId}/configs](/docs/api/linode-instances/#configuration-profiles-list) - endpoints and the LinodeConfig object for more information. example: 2 readOnly: true + gpus: + type: integer + description: | + The number of gpus this Linode has access to. + example: 0 + readOnly: true transfer: type: integer description: The amount of network transfer this Linode is allotted each month. @@ -23443,12 +23588,12 @@ components: Cost in US dollars, broken down into hourly and monthly charges. properties: hourly: - type: integer + type: number description: Cost (in US dollars) per hour. example: 0.03 x-linode-cli-display: 9 monthly: - type: integer + type: number description: Cost (in US dollars) per month. example: 20 x-linode-cli-display: 10 @@ -23470,12 +23615,12 @@ components: description: Cost of enabling Backups for this Linode Type. properties: hourly: - type: integer + type: number description: > The cost (in US dollars) per hour to add Backups service. example: 0.008 monthly: - type: integer + type: number description: > The cost (in US dollars) per month to add Backups service. example: 5 @@ -23586,7 +23731,7 @@ components: and the latest supported patch version will be deployed. x-linode-filterable: true x-linode-cli-display: 4 - example: "1.24" + example: "1.25" control_plane: type: object description: > @@ -23788,7 +23933,7 @@ components: A Kubernetes version number available for deployment to a Kubernetes cluster in the format of <major>.<minor>, and the latest supported patch version. - example: "1.24" + example: "1.25" LongviewClient: type: object description: > @@ -23906,17 +24051,27 @@ components: username: type: string description: > - The username of the User that was logged into. + The username of the User that attempted the login. example: example_user readOnly: true x-linode-cli-display: 4 + status: + type: string + enum: + - successful + - failed + description: | + Whether the login attempt succeeded or failed. + example: successful + readOnly: true + x-linode-cli-display: 5 restricted: type: boolean description: > - True if the User that was logged into was a restricted User, false otherwise. + True if the User that attempted the login was a restricted User, false otherwise. example: true readOnly: true - x-linode-cli-display: 5 + x-linode-cli-display: 6 LongviewSubscription: type: object description: > @@ -25886,12 +26041,18 @@ components: description: The unique ID of this Region. example: us-east x-linode-cli-display: 1 + label: + type: string + description: Detailed location information for this Region, including city, state or region, and country. + example: Newark, NJ, USA + readOnly: true + x-linode-cli-display: 2 country: type: string description: The country where this Region resides. example: us readOnly: true - x-linode-cli-display: 2 + x-linode-cli-display: 3 capabilities: type: array items: @@ -25904,7 +26065,7 @@ components: - Block Storage - Object Storage readOnly: true - x-linode-cli-display: 3 + x-linode-cli-display: 4 status: type: string description: > @@ -25914,11 +26075,11 @@ components: - ok - outage readOnly: true - x-linode-cli-display: 4 + x-linode-cli-display: 5 resolvers: type: object readOnly: true - x-linode-cli-display: 5 + x-linode-cli-display: 6 properties: ipv4: type: string diff --git a/sources b/sources index 87a3920..9db8f41 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -SHA512 (v5.28.1.tar.gz) = 92071c809b353454d18fdd8dd3c2ca00526f04b3732ee4c90a6e953dffc67bb56177fe4450e74bee67ca24e0b3e201353114fc2fd59abe078a78a9d2455f17b6 +SHA512 (v5.35.0.tar.gz) = 338ef420a1e2f0210330822212eec1e8b999510a449ffa1530c36823cebcb9269c37246efede235ec05a34cd178e0f56dd7f9b2acc994b5295ad9c065e3ed627