-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stack overflow. Repeat 611 times: Netlify deploy #1020
Comments
Interesting! Did you just add an empty appsettings.json file, or did it contain anything? It looks as though it failed in the deployment pipeline while trying to get a particular value (though it's hard to tell what value). I'm going to move this issue over to Statiq Web since that's where the deployment pipeline lives and continue investigating. |
Quick question - where are "NetlifySiteId" and "NetlifyAccessToken" defined? I see them being used to configure the Netlify deployment, but where are those values coming from? Were they defined anywhere before you added the appsettings.json file? |
Ah, I see what's going on here. Basically, the public static TBootstrapper DeployToNetlify<TBootstrapper>(
this TBootstrapper bootstrapper,
Config<string> siteId,
Config<string> accessToken)
where TBootstrapper : IBootstrapper =>
bootstrapper
.AddSettingsIfNonExisting(new Dictionary<string, object>
{
{ WebKeys.NetlifySiteId, siteId },
{ WebKeys.NetlifyAccessToken, accessToken }
}); See how it's just calling The "solution" here is to either specify the value of these settings directly in the I'll make a note in the documentation to clarify this for all the deployment pipelines, and I also made a small improvement to how this sort of recursive key expansion is reported so it's clearer. Here's what your scenario (without the |
…tional documentation regarding deployment pipelines and settings (statiqdev/Statiq.Web#1020).
…tional documentation regarding deployment pipelines and settings (statiqdev/Statiq.Web#1020).
I found this issue when deploying i forgot to add appsettings.json and this happened after adding the file it worked like a charm
program start
Steps to reproduce :
deploy -s IgnoreInvalidXrefs=true
The text was updated successfully, but these errors were encountered: