Ansible date variable

Question

I'm trying to learn how to use Ansible facts as variables, and I don't get it. When I run...

$ ansible localhost -m setup

...it lists all of the facts of my system. I selected one at random to try and use it, ansible_facts.ansible_date_time.date, but I can't figure out HOW to use it. When I run...

$ ansible localhost -m setup -a "filter=ansible_date_time"
localhost | success >> {
    "ansible_facts": {
        "ansible_date_time": {
            "date": "2015-07-09",
            "day": "09",
            "epoch": "1436460014",
            "hour": "10",
            "iso8601": "2015-07-09T16:40:14Z",
            "iso8601_micro": "2015-07-09T16:40:14.795637Z",
            "minute": "40",
            "month": "07",
            "second": "14",
            "time": "10:40:14",
            "tz": "MDT",
            "tz_offset": "-0600",
            "weekday": "Thursday",
            "year": "2015"
        }
    },
    "changed": false
}

So, it's CLEARLY there. But when I run...

$ ansible localhost -a "echo {{ ansible_facts.ansible_date_time.date }}"
localhost | FAILED => One or more undefined variables: 'ansible_facts' is undefined

$ ansible localhost -a "echo {{ ansible_date_time.date }}"
localhost | FAILED => One or more undefined variables: 'ansible_date_time' is undefined

$ ansible localhost -a "echo {{ date }}"
localhost | FAILED => One or more undefined variables: 'date' is undefined

What am I not getting here? How do I use Facts as variables?

score 101 · Accepted Answer · answered Jul 09 '15 at 17:02

The command ansible localhost -m setup basically says "run the setup module against localhost", and the setup module gathers the facts that you see in the output.

When you run the echo command these facts don't exist since the setup module wasn't run. A better method to testing things like this would be to use ansible-playbook to run a playbook that looks something like this:

- hosts: localhost
  tasks:
      - debug: var=ansible_date_time

      - debug: msg="the current date is {{ ansible_date_time.date }}"

Because this runs as a playbook facts for localhost are gathered before the tasks are run. The output of the above playbook will be something like this:

PLAY [localhost] **************************************************

GATHERING FACTS ***************************************************************
ok: [localhost]

TASK: [debug var=ansible_date_time] *******************************************
ok: [localhost] => {
    "ansible_date_time": {
        "date": "2015-07-09",
        "day": "09",
        "epoch": "1436461166",
        "hour": "16",
        "iso8601": "2015-07-09T16:59:26Z",
        "iso8601_micro": "2015-07-09T16:59:26.896629Z",
        "minute": "59",
        "month": "07",
        "second": "26",
        "time": "16:59:26",
        "tz": "UTC",
        "tz_offset": "+0000",
        "weekday": "Thursday",
        "year": "2015"
    }
}

TASK: [debug msg="the current date is {{ ansible_date_time.date }}"] **********
ok: [localhost] => {
    "msg": "the current date is 2015-07-09"
}

PLAY RECAP ********************************************************************
localhost      : ok=3    changed=0    unreachable=0    failed=0

score 25 · Answer 2 · edited Jun 19 '19 at 14:23

25

The lookup module of ansible works fine for me. The yml is:

- hosts: test
  vars:
    time: "{{ lookup('pipe', 'date -d \"1 day ago\" +\"%Y%m%d\"') }}"

You can replace any command with date to get result of the command.

edited Jun 19 '19 at 14:23

splash

13,037
1
44
67

answered Aug 04 '17 at 03:17

onebraveman

511
7
11

4

This solution is much shorter compared to other answers especially if you want to define something in date and time format. I have used something like `{{ lookup('pipe', 'date +%Y-%m-%d-%H-%M-%S')}}.sql`. Thanks – Kamal Soni Jun 01 '18 at 04:06
This is a good solution especially if you don't (or can't) gather facts from the host. – ascendants Dec 20 '19 at 20:37
But the downside of this method is that, vars are lazy evaluated, so if this var is accessed on the other day (maybe the playbook span over the midnight), the var will have different value – Eric Wong Mar 02 '21 at 08:16

score 6 · Answer 3 · answered Sep 13 '17 at 16:44

Note that the ansible command doesn't collect facts, but the ansible-playbook command does. When running ansible -m setup, the setup module happens to run the fact collection so you get the facts, but running ansible -m command does not. Therefore the facts aren't available. This is why the other answers include playbook YAML files and indicate the lookup works.

score 0 · Answer 4 · answered Apr 09 '18 at 05:00

0

The filter option filters only the first level subkey below ansible_facts

answered Apr 09 '18 at 05:00

Ghasem keshavarz haddad

1
3

score 0 · Answer 5 · answered May 27 '20 at 16:58

I tried the lookup('pipe,'date') method and got trouble when I push the playbook to the tower. The tower is somehow using UTC timezone. All play executed as early as the + hours of my TZ will give me one day later of the actual date.

For example: if my TZ is Asia/Manila I supposed to have UTC+8. If I execute the playbook earlier than 8:00am in Ansible Tower, the date will follow to what was in UTC+0. It took me a while until I found this case. It let me use the date option '-d \"+8 hours\" +%F'. Now it gives me the exact date that I wanted.

Below is the variable I set in my playbook:

  vars:
    cur_target_wd: "{{ lookup('pipe','date -d \"+8 hours\" +%Y/%m-%b/%d-%a') }}"

That will give me the value of "cur_target_wd = 2020/05-May/28-Thu" even I run it earlier than 8:00am now.

There is other way to make sure it apply a correct date regardless of were to run the playbook. **cur_target_wd: "{{ lookup('pipe','TZ=Asia/Manila date +%Y/%m-%b/%d-%a') }}" — Dyames, May 27 '20 at 21:28
Thank you so much I was looking exactly for that TZ notation. In my case I used TZ=Australia/Melbourne and it worked perfectly! — Bubzsan, Oct 02 '20 at 09:24

Ansible date variable

5 Answers5

Linked