Validate release date on continuous queues manager

Before performing the tasks on the job, we need to make sure that the
release date is properly configured on the job. This can be simply
done by making sure that the current date is not well past the end
of the on-sync date which is calculated by adding 4 weeks to the
configured release date. (Normally on-sync ends 2 weeks after the
release but setting it to 4 weeks just in case we have an unusually
longer on-sync period),

Author: junpataleta

tracker_automations/continuous_manage_queues/continuous_manage_queues.sh

@@ -72,7 +72,7 @@ movemax=${movemax:-3}
 lastweekdate=${lastweekdate:-$(date -d "${releasedate} -7day" +%Y-%m-%d)}
 dryrun=${dryrun:-}
 
-# Verify that $releasedata has a correct YYYY-MM-DD format
+# Verify that $releasedate has a correct YYYY-MM-DD format
 if [[ ! ${releasedate} =~ ^[0-9]{4}-[0-9]{2}-[0-9]{2}$ ]]; then
     echo "ERROR: \$releasedate. Incorrect YYYY-MM-DD format detected: ${releasedate}"
     exit 1
@@ -87,6 +87,13 @@ fi
 # Today
 nowdate=$(date +%Y%m%d)
 
+# Verify that the current date is not well past the on-sync period. (Normally 2 weeks but making it 4 weeks just in case).
+onsyncenddate=$(date -d "${releasedate} +28day" +%Y%m%d)
+if [ $nowdate -gt $onsyncenddate ]; then
+    echo "ERROR: The current date is already past the on-sync period. Please make sure the Release date ($releasedate) is configured correctly."
+    exit 1
+fi
+
 # Decide if we are going to proceed with behaviour A (before release) or behaviour B (after release)
 behaviorAB=
 if [ $nowdate -lt $(date -d "${releasedate}" +%Y%m%d) ]; then