secureApiKey on gatsby-config not work

[blasiuscosa]

Brief bug description

When I had my 'Delivery API secured access' enabled and provided secureApiKey with the Delivery API key

Repro steps

1. Run gatsby develop
2. Monitor the terminal
3. See error

Expected behavior

What the correct behavior is? This should work by generating the node for each content types and content items

Test environment

• Windows 10 Subsystem for Linux (Ubuntu 18.04)
• Gatsby CLI version: 2.7.47
• Gatsby version: 2.15.14
• gatsby-source-kentico-cloud 3.1.0

Additional context

Screenshots

[Simply007]

hello @blasiuscosa,

thanks, for reporting the issue! (I have also checked the Intercom conversation with @giorgioLUK)

This was most probably caused by incorrect links to JavaScript Delivery SDK (caused by the rebranding of Kentico Kontent). I have fixed the readme links in this commit: https://github.com/Kentico/gatsby-source-kentico-cloud/commit/f0264fe3ad2b3b776998b755976a08d36fb5db39

The correct delivery format is described here:

• https://github.com/Kentico/kentico-kontent-js/blob/delivery%405.7.2/packages/delivery/DOCS.md#secured-delivery-api-mode

As I see you are using secureApiKey - you should use securedApiKey (with the'd').

I have created a sample under my personal profile:

• https://github.com/Simply007/gatsby-with-kontent-secured-api

You could clone is and run:

npm install
npm run develop

There is already set up the sample project with secured API turned on (no sensitive data here :smile:) Check gatsby-config.js.

You could try this for testing for by setting your project ID and secured API key.

Let me know if this helps! If not - feel free to reopen the issue.

[blasiuscosa]

Hi @Simply007,

Thank you for the updates, yes I was looked on the JavaScript Delivery SDK link on readme file. This is really helpful and now it works properly.