conflict config/credentials/test.key during Jumpstart initial configuration in Admin UI

Hi there!

Whenever I attempt to save my configuration settings in the Jumpstart Pro Admin area the save button gets stuck on "Saving..." and I get the following error in terminal: 

conflict  config/credentials/test.key

I tried reinstalling the app and only checking the Stripe payment processor option during configuration and clicking Save. I still had the same issue and error. 

I was able to get around this issue by my removing the initial test.key and test.yml.enc files from the config/credentials folder. After updating my Stripe Key in the locations below, the error returned when I attempted to change my business name and click 'Save'.

rails credentials:edit --environment development
rails credentials:edit --environment test
rails credentials:edit --environment staging
rails credentials:edit --environment production

Is there a step in the set-up process I'm missing?

Thanks for your help! 

Michael Marais  This might be a bug I introduced accidentally last week. I updated the Admin area so that it would auto-generate credentials for each environment if they didn't exist. There might be something wrong there. Going to take a look shortly and see what's going on. 👍

Yep - I ran into this this morning with the same behavior. Rails warns of a key conflict and when I (naively) accepted the jumpstart-generated versions, I wasn't able to unencrypt them: "Couldn't decrypt config/credentials/development.yml.enc. Perhaps you passed the wrong key?"

I worked around it by starting from scratch with my keys and not accepting the key conflicts the second time around :) 

Alright, I just pushed an update to have it only generate credentials if the "environment.yml.enc" file exists. That way it shouldn't ever try to override existing credentials.

Can you guys pull down that change and double check that it fixes the issue for you?

Chris Oliver This does fix the issue for me, thank you! 

A related issue: I notice that Jumpstart is also rewriting my `config/sidekiq.yml` file and my `Procfile` as well when saving the configuration -- not too big a deal, a minor inconvenience.

Basically Jumpstart wants to reset my sidekiq timeout back to 30 from 8 and remove the `release` command from my Procfile if I update my Jumpstart config each time.  

Jason Eastwood I updated it so it wouldn't override the sidekiq file. That was definitely a bug. 

Fixing the Procfile overrides is coming shortly, but it's a little more involved since we actually should substitute individual lines of the file rather than create if it doesn't exist like most other configs.

Thanks, Chris!