Dropped LongviewSubscription from AccountSettingsUpdateOptions

[ezilber-akamai-zz]

📝 Description

Dropped LongviewSubscription from AccountSettingsUpdateOptions.

[yec-akamai]

Why do we need to remove LongviewSubscription from the update options? It seems longview_subscription is still available in the api doc https://www.linode.com/docs/api/account/#account-settings-update

[ezilber-akamai-zz]

Why do we need to remove LongviewSubscription from the update options? It seems longview_subscription is still available in the api doc https://www.linode.com/docs/api/account/#account-settings-update

According to the ticket description LongviewSubscription can no longer be updated through this endpoint.

[yec-akamai]

I see. Is it possible to mark this field deprecated, and add a comment to point user to use PUT /longview/plan? I'm wondering if directly remove it can cause a breaking change.

[lgarber-akamai]

Just to add a bit of context, this field can no longer be sent to the API since the API now returns the following error if longview_subscription is specified:

longview_subscription editing at this location is no longer available. Please use the /longview/plan endpoint instead.

It might still be worth keeping the field to prevent introducing a breaking change for downstream consumers, but it might be worth considering to notify users of the non-functional endpoint. Does anyone have any thoughts on this? 🙂

[ezilber-akamai-zz]

Just to add a bit of context, this field can no longer be sent to the API since the API now returns the following error if longview_subscription is specified:

longview_subscription editing at this location is no longer available. Please use the /longview/plan endpoint instead.

It might still be worth keeping the field to prevent introducing a breaking change for downstream consumers, but it might be worth considering to notify users of the non-functional endpoint. Does anyone have any thoughts on this? 🙂

Would a deprecation notice in a comment be enough of a notification for users?

[yec-akamai]

Maybe we can highlight this change in the corresponding release and let the user know the potential breaking change or the API doesn't work this way anymore. I'm also thinking we should let the API doc team know and update the doc as well to reduce confusion.

[ezilber-akamai-zz]

I agree that we should probably keep the field to avoid any breaking changes, and I think adding a note to the release is a great idea!

[lgarber-akamai]

Looks good!