tlsSubscriptions.listTlsSubs returns a list of empty objects with no data.

[ieb]

Version
v6.0.0

What happened

      const tlsSubscriptions = new Fastly.TlsSubscriptionsApi();
      
      const list = await tlsSubscriptions.listTlsSubs({
				            include: 'tls_authorizations',
				            page_number: 1,
				            page_size: 20,
				            sort: 'created_at',
				          });
      console.log(list.data);

Produces

        [
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {},
          TlsSubscriptionResponse {}
        ]

All the elements returned are empty and have no data.
Which makes it a bit hard to inspect a subscription.

I would have expected them to show data.
API Key has engineer global access to the account with TLS permissions granted.

[ieb]

TlstSubscriptionResponse.constructFromObject assumes that data is in data.data but data returned is

    {
      id: 'XXXX',
      type: 'tls_subscription',
      attributes: {
        certificate_authority: 'lets-encrypt',
        created_at: '2023-06-23T17:12:15.000Z',
        state: 'issued',
        has_active_order: false,
        updated_at: '2023-07-13T20:44:10.000Z'
      },
      relationships: {
        tls_authorizations: { data: [Array] },
        tls_certificates: { data: [Array] },
        tls_domains: { data: [Array] },
        common_name: { data: [Object] },
        tls_configuration: { data: [Object] }
      }
    }

Not in data.data... but some API calls do have data.data eg getTlsSub

Hacking the generated code lines 58-69. TlsSubscriptionResponse.js to

            value: function constructFromObject(data, obj) {
  if (data) {
    obj = obj || new TlsSubscriptionResponse();
    if (data.hasOwnProperty('data')) {
      obj['data'] = _TlsSubscriptionResponseData["default"].constructFromObject(data['data']);
    } else {
      obj['data'] = _TlsSubscriptionResponseData["default"].constructFromObject(data);
    }
  }
  return obj;
}

Proper fix would be better than hacking, but IIUC the code is generated so PR isnt of any value.

[ieb]

And there is nothing to handle relationships in the API which is is vital to be able to manage subscripts.

Also the included data is missing. I have hacked the npm further. TBH it might be better if I use the API directly as a work round.

[ieb]

This appears to be a viable work around that gives access to the subscription and authorisations with no hacks to the npm package.

				const http_out = await tlsSubscriptions.listTlsSubsWithHttpInfo({
				  include: 'tls_authorizations',
				  page_number: 1,
				  page_size: 20,
				  sort: 'created_at',
				});
				const list = http_out.response.body;

[Integralist]

Hi @ieb

Thanks for opening this issue.

Sounds like there is an issue with the OpenAPI schemas that the API client is being generated from.

We'll create a ticket internally to track this.