Respect existing deploy config
See original GitHub issueThe adapter-vercel
package completely obliterates the existing vercel.json
file.
Instead it should be write the necessary values into the JSON object, only after checking that the necessary keys/values don’t already exist.
Option B is to add some kind of adapter-vercel
config or CLI flag that effectively acts like --skip-config
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Config as Code strategies
Review and collaborate on changes using pull requests. Clone an existing project to use as a template for future projects. Track changes to...
Read more >Configuration deployment from Workbench over an ...
When deploying a configuration from Workbench onto a server with an existing configuration you should first reinitialize the server.
Read more >Environments and deployments - GitLab Docs
By default, GitLab assumes a tier based on the environment name. Instead, you can use the deployment_tier keyword to specify a tier. Configure...
Read more >Cisco Secure Firewall Management Center Device ...
This procedure resets the threat defense configuration to factory defaults by changing manager from management center to local and configuring ...
Read more >Deploy configuration changes
Review the list of your existing deployments and compare deployed configurations. Deployments are the configuration changes that you implemented by clicking ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Rich-Harris It’s still relevant for e.g. the Netlify Adapter I guess. Because there the potentially already existing
_redirects
file is “overridden” (actually just ignored and thus not applied). The adapter’s_redirects
has a higher priority thannetlify.toml
though, so currently any configured redirect rule doesn’t work (see discussion at https://github.com/sveltejs/kit/issues/930#issuecomment-817077432).i think we can close this now, since we don’t write a
vercel.json
. reopen if i’m mistaken