Sidekiq service not loaded on first Chef run

[dvalfre]

So, this line reloads the systemctl unit for Sidekiq only if the config file is there. This behavior prevents systemd to continuously trying to load a service that it's not ready yet.
But, on new instances, turns out it also prevents loading the service after the code has been deployed. This is because on new instances the first Chef run is a full config one, but the one after the code has been deployed is a shorter one which doesn't start the Sidekiq service.
It's clear then that this logic should be revisited.