Don’t force cable.yml config

[jkostolansky]

I was just migrating a Rails app to Solid Trifecta, and I noticed an inconsistency in the installation process. Solid Cache and Solid Queue asked me if I wanted to overwrite my existing config files, but Solid Cable did not, it replaced the already manually edited config.yml file without asking.

If there isn't any other reason to keep the force option enabled, I propose that we disable it.

Relevant files:

• Solid Queue
• Solid Cache

[jeromedalbert]

I believe this PR introduces a regression in that it now blocks rails new as of yesterday's 3.0.6 release. Steps to repro:

$ rails new myapp

...
    conflict  config/cable.yml
Overwrite /Users/jerome/c/tmp/myapp/config/cable.yml? (enter "h" for help) [Ynaqdhm]

@npezza93 Should this be hotfixed/reverted and a new version released while deciding a better course of action, or what do you recommend?

[npezza93]

Ugh yea good catch @jeromedalbert. I've reverted and cut a new release. @jkostolansky looks like we cant do this because rails currently manages the cable.yml file on creation. Whereas it does control cache.yml and queue.yml for the other solids. Thanks again for catching @jeromedalbert

[jeromedalbert]

Thank you for the super quick revert @npezza93! ❤️

Wondering if maybe the fix would be for Rails to skip creating cable.yml if solid is enabled.