IssueTracker

What you would like to accomplish:

Ability to use time and date macros like YEAR, MONTH, DAY, HOUR and MINUTE of the Cloud Scheduler job invocation time in HttpTarget fields uri, headers and body.

This would allow for example elegant scheduled Cloud SQL exports using the Cloud SQL API directly, without the use of Cloud Functions.

How this might work:

Create a job that creates a Cloud SQL export using date and time macros in the export file name:

cat << EOF > exportcontext.json
{
  "exportContext": {
    "kind": "sql#exportContext",
    "fileType": "SQL",
    "uri": "gs://my-example-export-bucket/myexampledb_$YEAR$MONTH$DAY_$HOUR$MINUTE.sql.gz",
    "databases": ["myexampledb"]
  }
}
EOF

gcloud scheduler jobs create http sql-export \
--schedule="0 */3 * * *" \
--uri="https://sqladmin.googleapis.com/sql/v1beta4/projects/myproj-123456789/instances/mymaster/export" \
--http-method=POST \
--message-body-from-file=exportcontext.json \
--oauth-service-account-email="sqlexport@myproj-123456789.iam.gserviceaccount.com"

If applicable, reasons why alternative solutions are not sufficient:

One could create a Cloud Functions method as a "proxy" for the API call to use macros/variables there but this makes things much more complicated. No-code approach of the Cloud Scheduler calling Google Cloud APIs directly should be preferred.

Other information (workarounds you have tried, documentation consulted, etc):

https://cloud.google.com/scheduler/docs/reference/rpc/google.cloud.scheduler.v1beta1