|
console.error("improperly configured entry for '${kvStoreName}' in fastly.toml"); |
If the fastly.toml file happens to contain the string matching the name of the configured KV Store, anywhere in the file, then this check will cause the build to fail. In my case I used the same string for the project's name as for the KV Store, so this check fails every time if the build has not previously put a list of assets into the fastly.toml file.
I suspect this check was put in place to catch situations where the user had their own configuration for the KV Store already present in fastly.toml, but the check is too 'greedy' as it is now.