Feature #8997

Write YAML files to describe the cronjob needed for each reminder

Added by sajolida 2015-03-03 11:01:48 . Updated 2015-04-18 08:28:06 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_1.4
Start date:
2015-03-03
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Files

lhf.yaml (1458 B) sajolida, 2015-03-03 14:13:40
monthly.yaml (1547 B) sajolida, 2015-03-03 14:13:40

Subtasks

History

#1 Updated by sajolida 2015-03-03 14:15:19

  • File lhf.yaml added
  • File monthly.yaml added
  • Assignee changed from sajolida to intrigeri
  • QA Check set to Ready for QA

Would this work? I didn’t check the YAML syntax very carefully this time. But it’s just to be sure we agree on what needs to be done.

Note that:

  • $DATE in the subject must be replaced by the “date” attribute.
  • In the “date” attribute I left the \ escaping for cron. So the command don’t run fine if copy-pasted from there.

#2 Updated by intrigeri 2015-03-03 15:04:22

> Would this work?

I think it should work, but I’ve no past experience with Hiera so I cannot really tell.

> Note that:

> * $DATE in the subject must be replaced by the “date” attribute.
> * In the “date” attribute I left the \ escaping for cron. So the command don’t run fine if copy-pasted from there.

OK. May you please dump the relevant info and attachments to Feature #7763, where it can be used as hints for implementation?

#3 Updated by BitingBird 2015-04-10 16:21:20

This is ready for QA -> should it have a milestone?

#4 Updated by intrigeri 2015-04-11 09:51:56

  • Target version set to Tails_1.4

Indeed.

#5 Updated by intrigeri 2015-04-18 08:28:07

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100
  • QA Check changed from Ready for QA to Pass