Replies: 2 comments 3 replies
-
The issue already contained a few comments, especially by @ardentsword, that are relevant to the status. |
Beta Was this translation helpful? Give feedback.
0 replies
-
so the problem only with migration from previous recipe to current? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Migrated from issue #3768
Deployer Version
v7.3.3
Target OS
Ubuntu 22.04
Which PHP version are you using?
PHP 8.2
Content of deploy.php or deploy.yaml
Steps to reproduce
We've been using the
crontab
recipe in our config for some time now, and I welcome the rewrite with sections, as it prevents duplicate entries when the crontab config is changed and resynced.Without initially knowing about the change, it broke some of our applications and no crontab was running for some time. Only the terminal output messages, pointed me towards the new behavior. I get that this is only a change in a smaller recipe, but it seems to be a breaking change.
If there is a migration in place, it shouldn't be an issue. However, I noted some issues while using it and migrating existing applications to it.
Running the
crontab:sync
task showed it recognized a previous job in the crontab config on the server, said it would move it to the section, said it couldn't find the section, and said it would create the section.The section was created, and the previous job was removed. However, the pre-existing job was not created anew in the new section. It seems like it cannot perform the migration and creation of a new section at the same time, breaking existing configurations.
The fix is to run the
crontab:sync
task again, which fixes the problem.Before:
Migration:
Re-run:
Beta Was this translation helpful? Give feedback.
All reactions