1.. _vars_and_facts: 2 3************************************************ 4Discovering variables: facts and magic variables 5************************************************ 6 7With Ansible you can retrieve or discover certain variables containing information about your remote systems or about Ansible itself. Variables related to remote systems are called facts. With facts, you can use the behavior or state of one system as configuration on other systems. For example, you can use the IP address of one system as a configuration value on another system. Variables related to Ansible are called magic variables. 8 9.. contents:: 10 :local: 11 12Ansible facts 13============= 14 15Ansible facts are data related to your remote systems, including operating systems, IP addresses, attached filesystems, and more. You can access this data in the ``ansible_facts`` variable. By default, you can also access some Ansible facts as top-level variables with the ``ansible_`` prefix. You can disable this behavior using the :ref:`INJECT_FACTS_AS_VARS` setting. To see all available facts, add this task to a play:: 16 17 - name: Print all available facts 18 ansible.builtin.debug: 19 var: ansible_facts 20 21To see the 'raw' information as gathered, run this command at the command line:: 22 23 ansible <hostname> -m ansible.builtin.setup 24 25Facts include a large amount of variable data, which may look like this: 26 27.. code-block:: json 28 29 { 30 "ansible_all_ipv4_addresses": [ 31 "REDACTED IP ADDRESS" 32 ], 33 "ansible_all_ipv6_addresses": [ 34 "REDACTED IPV6 ADDRESS" 35 ], 36 "ansible_apparmor": { 37 "status": "disabled" 38 }, 39 "ansible_architecture": "x86_64", 40 "ansible_bios_date": "11/28/2013", 41 "ansible_bios_version": "4.1.5", 42 "ansible_cmdline": { 43 "BOOT_IMAGE": "/boot/vmlinuz-3.10.0-862.14.4.el7.x86_64", 44 "console": "ttyS0,115200", 45 "no_timer_check": true, 46 "nofb": true, 47 "nomodeset": true, 48 "ro": true, 49 "root": "LABEL=cloudimg-rootfs", 50 "vga": "normal" 51 }, 52 "ansible_date_time": { 53 "date": "2018-10-25", 54 "day": "25", 55 "epoch": "1540469324", 56 "hour": "12", 57 "iso8601": "2018-10-25T12:08:44Z", 58 "iso8601_basic": "20181025T120844109754", 59 "iso8601_basic_short": "20181025T120844", 60 "iso8601_micro": "2018-10-25T12:08:44.109968Z", 61 "minute": "08", 62 "month": "10", 63 "second": "44", 64 "time": "12:08:44", 65 "tz": "UTC", 66 "tz_offset": "+0000", 67 "weekday": "Thursday", 68 "weekday_number": "4", 69 "weeknumber": "43", 70 "year": "2018" 71 }, 72 "ansible_default_ipv4": { 73 "address": "REDACTED", 74 "alias": "eth0", 75 "broadcast": "REDACTED", 76 "gateway": "REDACTED", 77 "interface": "eth0", 78 "macaddress": "REDACTED", 79 "mtu": 1500, 80 "netmask": "255.255.255.0", 81 "network": "REDACTED", 82 "type": "ether" 83 }, 84 "ansible_default_ipv6": {}, 85 "ansible_device_links": { 86 "ids": {}, 87 "labels": { 88 "xvda1": [ 89 "cloudimg-rootfs" 90 ], 91 "xvdd": [ 92 "config-2" 93 ] 94 }, 95 "masters": {}, 96 "uuids": { 97 "xvda1": [ 98 "cac81d61-d0f8-4b47-84aa-b48798239164" 99 ], 100 "xvdd": [ 101 "2018-10-25-12-05-57-00" 102 ] 103 } 104 }, 105 "ansible_devices": { 106 "xvda": { 107 "holders": [], 108 "host": "", 109 "links": { 110 "ids": [], 111 "labels": [], 112 "masters": [], 113 "uuids": [] 114 }, 115 "model": null, 116 "partitions": { 117 "xvda1": { 118 "holders": [], 119 "links": { 120 "ids": [], 121 "labels": [ 122 "cloudimg-rootfs" 123 ], 124 "masters": [], 125 "uuids": [ 126 "cac81d61-d0f8-4b47-84aa-b48798239164" 127 ] 128 }, 129 "sectors": "83883999", 130 "sectorsize": 512, 131 "size": "40.00 GB", 132 "start": "2048", 133 "uuid": "cac81d61-d0f8-4b47-84aa-b48798239164" 134 } 135 }, 136 "removable": "0", 137 "rotational": "0", 138 "sas_address": null, 139 "sas_device_handle": null, 140 "scheduler_mode": "deadline", 141 "sectors": "83886080", 142 "sectorsize": "512", 143 "size": "40.00 GB", 144 "support_discard": "0", 145 "vendor": null, 146 "virtual": 1 147 }, 148 "xvdd": { 149 "holders": [], 150 "host": "", 151 "links": { 152 "ids": [], 153 "labels": [ 154 "config-2" 155 ], 156 "masters": [], 157 "uuids": [ 158 "2018-10-25-12-05-57-00" 159 ] 160 }, 161 "model": null, 162 "partitions": {}, 163 "removable": "0", 164 "rotational": "0", 165 "sas_address": null, 166 "sas_device_handle": null, 167 "scheduler_mode": "deadline", 168 "sectors": "131072", 169 "sectorsize": "512", 170 "size": "64.00 MB", 171 "support_discard": "0", 172 "vendor": null, 173 "virtual": 1 174 }, 175 "xvde": { 176 "holders": [], 177 "host": "", 178 "links": { 179 "ids": [], 180 "labels": [], 181 "masters": [], 182 "uuids": [] 183 }, 184 "model": null, 185 "partitions": { 186 "xvde1": { 187 "holders": [], 188 "links": { 189 "ids": [], 190 "labels": [], 191 "masters": [], 192 "uuids": [] 193 }, 194 "sectors": "167770112", 195 "sectorsize": 512, 196 "size": "80.00 GB", 197 "start": "2048", 198 "uuid": null 199 } 200 }, 201 "removable": "0", 202 "rotational": "0", 203 "sas_address": null, 204 "sas_device_handle": null, 205 "scheduler_mode": "deadline", 206 "sectors": "167772160", 207 "sectorsize": "512", 208 "size": "80.00 GB", 209 "support_discard": "0", 210 "vendor": null, 211 "virtual": 1 212 } 213 }, 214 "ansible_distribution": "CentOS", 215 "ansible_distribution_file_parsed": true, 216 "ansible_distribution_file_path": "/etc/redhat-release", 217 "ansible_distribution_file_variety": "RedHat", 218 "ansible_distribution_major_version": "7", 219 "ansible_distribution_release": "Core", 220 "ansible_distribution_version": "7.5.1804", 221 "ansible_dns": { 222 "nameservers": [ 223 "127.0.0.1" 224 ] 225 }, 226 "ansible_domain": "", 227 "ansible_effective_group_id": 1000, 228 "ansible_effective_user_id": 1000, 229 "ansible_env": { 230 "HOME": "/home/zuul", 231 "LANG": "en_US.UTF-8", 232 "LESSOPEN": "||/usr/bin/lesspipe.sh %s", 233 "LOGNAME": "zuul", 234 "MAIL": "/var/mail/zuul", 235 "PATH": "/usr/local/bin:/usr/bin", 236 "PWD": "/home/zuul", 237 "SELINUX_LEVEL_REQUESTED": "", 238 "SELINUX_ROLE_REQUESTED": "", 239 "SELINUX_USE_CURRENT_RANGE": "", 240 "SHELL": "/bin/bash", 241 "SHLVL": "2", 242 "SSH_CLIENT": "REDACTED 55672 22", 243 "SSH_CONNECTION": "REDACTED 55672 REDACTED 22", 244 "USER": "zuul", 245 "XDG_RUNTIME_DIR": "/run/user/1000", 246 "XDG_SESSION_ID": "1", 247 "_": "/usr/bin/python2" 248 }, 249 "ansible_eth0": { 250 "active": true, 251 "device": "eth0", 252 "ipv4": { 253 "address": "REDACTED", 254 "broadcast": "REDACTED", 255 "netmask": "255.255.255.0", 256 "network": "REDACTED" 257 }, 258 "ipv6": [ 259 { 260 "address": "REDACTED", 261 "prefix": "64", 262 "scope": "link" 263 } 264 ], 265 "macaddress": "REDACTED", 266 "module": "xen_netfront", 267 "mtu": 1500, 268 "pciid": "vif-0", 269 "promisc": false, 270 "type": "ether" 271 }, 272 "ansible_eth1": { 273 "active": true, 274 "device": "eth1", 275 "ipv4": { 276 "address": "REDACTED", 277 "broadcast": "REDACTED", 278 "netmask": "255.255.224.0", 279 "network": "REDACTED" 280 }, 281 "ipv6": [ 282 { 283 "address": "REDACTED", 284 "prefix": "64", 285 "scope": "link" 286 } 287 ], 288 "macaddress": "REDACTED", 289 "module": "xen_netfront", 290 "mtu": 1500, 291 "pciid": "vif-1", 292 "promisc": false, 293 "type": "ether" 294 }, 295 "ansible_fips": false, 296 "ansible_form_factor": "Other", 297 "ansible_fqdn": "centos-7-rax-dfw-0003427354", 298 "ansible_hostname": "centos-7-rax-dfw-0003427354", 299 "ansible_interfaces": [ 300 "lo", 301 "eth1", 302 "eth0" 303 ], 304 "ansible_is_chroot": false, 305 "ansible_kernel": "3.10.0-862.14.4.el7.x86_64", 306 "ansible_lo": { 307 "active": true, 308 "device": "lo", 309 "ipv4": { 310 "address": "127.0.0.1", 311 "broadcast": "host", 312 "netmask": "255.0.0.0", 313 "network": "127.0.0.0" 314 }, 315 "ipv6": [ 316 { 317 "address": "::1", 318 "prefix": "128", 319 "scope": "host" 320 } 321 ], 322 "mtu": 65536, 323 "promisc": false, 324 "type": "loopback" 325 }, 326 "ansible_local": {}, 327 "ansible_lsb": { 328 "codename": "Core", 329 "description": "CentOS Linux release 7.5.1804 (Core)", 330 "id": "CentOS", 331 "major_release": "7", 332 "release": "7.5.1804" 333 }, 334 "ansible_machine": "x86_64", 335 "ansible_machine_id": "2db133253c984c82aef2fafcce6f2bed", 336 "ansible_memfree_mb": 7709, 337 "ansible_memory_mb": { 338 "nocache": { 339 "free": 7804, 340 "used": 173 341 }, 342 "real": { 343 "free": 7709, 344 "total": 7977, 345 "used": 268 346 }, 347 "swap": { 348 "cached": 0, 349 "free": 0, 350 "total": 0, 351 "used": 0 352 } 353 }, 354 "ansible_memtotal_mb": 7977, 355 "ansible_mounts": [ 356 { 357 "block_available": 7220998, 358 "block_size": 4096, 359 "block_total": 9817227, 360 "block_used": 2596229, 361 "device": "/dev/xvda1", 362 "fstype": "ext4", 363 "inode_available": 10052341, 364 "inode_total": 10419200, 365 "inode_used": 366859, 366 "mount": "/", 367 "options": "rw,seclabel,relatime,data=ordered", 368 "size_available": 29577207808, 369 "size_total": 40211361792, 370 "uuid": "cac81d61-d0f8-4b47-84aa-b48798239164" 371 }, 372 { 373 "block_available": 0, 374 "block_size": 2048, 375 "block_total": 252, 376 "block_used": 252, 377 "device": "/dev/xvdd", 378 "fstype": "iso9660", 379 "inode_available": 0, 380 "inode_total": 0, 381 "inode_used": 0, 382 "mount": "/mnt/config", 383 "options": "ro,relatime,mode=0700", 384 "size_available": 0, 385 "size_total": 516096, 386 "uuid": "2018-10-25-12-05-57-00" 387 } 388 ], 389 "ansible_nodename": "centos-7-rax-dfw-0003427354", 390 "ansible_os_family": "RedHat", 391 "ansible_pkg_mgr": "yum", 392 "ansible_processor": [ 393 "0", 394 "GenuineIntel", 395 "Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz", 396 "1", 397 "GenuineIntel", 398 "Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz", 399 "2", 400 "GenuineIntel", 401 "Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz", 402 "3", 403 "GenuineIntel", 404 "Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz", 405 "4", 406 "GenuineIntel", 407 "Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz", 408 "5", 409 "GenuineIntel", 410 "Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz", 411 "6", 412 "GenuineIntel", 413 "Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz", 414 "7", 415 "GenuineIntel", 416 "Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz" 417 ], 418 "ansible_processor_cores": 8, 419 "ansible_processor_count": 8, 420 "ansible_processor_nproc": 8, 421 "ansible_processor_threads_per_core": 1, 422 "ansible_processor_vcpus": 8, 423 "ansible_product_name": "HVM domU", 424 "ansible_product_serial": "REDACTED", 425 "ansible_product_uuid": "REDACTED", 426 "ansible_product_version": "4.1.5", 427 "ansible_python": { 428 "executable": "/usr/bin/python2", 429 "has_sslcontext": true, 430 "type": "CPython", 431 "version": { 432 "major": 2, 433 "micro": 5, 434 "minor": 7, 435 "releaselevel": "final", 436 "serial": 0 437 }, 438 "version_info": [ 439 2, 440 7, 441 5, 442 "final", 443 0 444 ] 445 }, 446 "ansible_python_version": "2.7.5", 447 "ansible_real_group_id": 1000, 448 "ansible_real_user_id": 1000, 449 "ansible_selinux": { 450 "config_mode": "enforcing", 451 "mode": "enforcing", 452 "policyvers": 31, 453 "status": "enabled", 454 "type": "targeted" 455 }, 456 "ansible_selinux_python_present": true, 457 "ansible_service_mgr": "systemd", 458 "ansible_ssh_host_key_ecdsa_public": "REDACTED KEY VALUE", 459 "ansible_ssh_host_key_ed25519_public": "REDACTED KEY VALUE", 460 "ansible_ssh_host_key_rsa_public": "REDACTED KEY VALUE", 461 "ansible_swapfree_mb": 0, 462 "ansible_swaptotal_mb": 0, 463 "ansible_system": "Linux", 464 "ansible_system_capabilities": [ 465 "" 466 ], 467 "ansible_system_capabilities_enforced": "True", 468 "ansible_system_vendor": "Xen", 469 "ansible_uptime_seconds": 151, 470 "ansible_user_dir": "/home/zuul", 471 "ansible_user_gecos": "", 472 "ansible_user_gid": 1000, 473 "ansible_user_id": "zuul", 474 "ansible_user_shell": "/bin/bash", 475 "ansible_user_uid": 1000, 476 "ansible_userspace_architecture": "x86_64", 477 "ansible_userspace_bits": "64", 478 "ansible_virtualization_role": "guest", 479 "ansible_virtualization_type": "xen", 480 "gather_subset": [ 481 "all" 482 ], 483 "module_setup": true 484 } 485 486You can reference the model of the first disk in the facts shown above in a template or playbook as:: 487 488 {{ ansible_facts['devices']['xvda']['model'] }} 489 490To reference the system hostname:: 491 492 {{ ansible_facts['nodename'] }} 493 494You can use facts in conditionals (see :ref:`playbooks_conditionals`) and also in templates. You can also use facts to create dynamic groups of hosts that match particular criteria, see the :ref:`group_by module <group_by_module>` documentation for details. 495 496.. _fact_requirements: 497 498Package requirements for fact gathering 499--------------------------------------- 500 501On some distros, you may see missing fact values or facts set to default values because the packages that support gathering those facts are not installed by default. You can install the necessary packages on your remote hosts using the OS package manager. Known dependencies include: 502 503* Linux Network fact gathering - Depends on the ``ip`` binary, commonly included in the ``iproute2`` package. 504 505.. _fact_caching: 506 507Caching facts 508------------- 509 510Like registered variables, facts are stored in memory by default. However, unlike registered variables, facts can be gathered independently and cached for repeated use. With cached facts, you can refer to facts from one system when configuring a second system, even if Ansible executes the current play on the second system first. For example:: 511 512 {{ hostvars['asdf.example.com']['ansible_facts']['os_family'] }} 513 514Caching is controlled by the cache plugins. By default, Ansible uses the memory cache plugin, which stores facts in memory for the duration of the current playbook run. To retain Ansible facts for repeated use, select a different cache plugin. See :ref:`cache_plugins` for details. 515 516Fact caching can improve performance. If you manage thousands of hosts, you can configure fact caching to run nightly, then manage configuration on a smaller set of servers periodically throughout the day. With cached facts, you have access to variables and information about all hosts even when you are only managing a small number of servers. 517 518.. _disabling_facts: 519 520Disabling facts 521--------------- 522 523By default, Ansible gathers facts at the beginning of each play. If you do not need to gather facts (for example, if you know everything about your systems centrally), you can turn off fact gathering at the play level to improve scalability. Disabling facts may particularly improve performance in push mode with very large numbers of systems, or if you are using Ansible on experimental platforms. To disable fact gathering:: 524 525 - hosts: whatever 526 gather_facts: no 527 528Adding custom facts 529------------------- 530 531The setup module in Ansible automatically discovers a standard set of facts about each host. If you want to add custom values to your facts, you can write a custom facts module, set temporary facts with a ``ansible.builtin.set_fact`` task, or provide permanent custom facts using the facts.d directory. 532 533.. _local_facts: 534 535facts.d or local facts 536^^^^^^^^^^^^^^^^^^^^^^ 537 538.. versionadded:: 1.3 539 540You can add static custom facts by adding static files to facts.d, or add dynamic facts by adding executable scripts to facts.d. For example, you can add a list of all users on a host to your facts by creating and running a script in facts.d. 541 542To use facts.d, create an ``/usr/local/etc/ansible/facts.d`` directory on the remote host or hosts. If you prefer a different directory, create it and specify it using the ``fact_path`` play keyword. Add files to the directory to supply your custom facts. All file names must end with ``.fact``. The files can be JSON, INI, or executable files returning JSON. 543 544To add static facts, simply add a file with the ``.facts`` extension. For example, create ``/usr/local/etc/ansible/facts.d/preferences.fact`` with this content:: 545 546 [general] 547 asdf=1 548 bar=2 549 550The next time fact gathering runs, your facts will include a hash variable fact named ``general`` with ``asdf`` and ``bar`` as members. To validate this, run the following:: 551 552 ansible <hostname> -m ansible.builtin.setup -a "filter=ansible_local" 553 554And you will see your custom fact added:: 555 556 "ansible_local": { 557 "preferences": { 558 "general": { 559 "asdf" : "1", 560 "bar" : "2" 561 } 562 } 563 } 564 565The ansible_local namespace separates custom facts created by facts.d from system facts or variables defined elsewhere in the playbook, so variables will not override each other. You can access this custom fact in a template or playbook as:: 566 567 {{ ansible_local['preferences']['general']['asdf'] }} 568 569.. note:: The key part in the key=value pairs will be converted into lowercase inside the ansible_local variable. Using the example above, if the ini file contained ``XYZ=3`` in the ``[general]`` section, then you should expect to access it as: ``{{ ansible_local['preferences']['general']['xyz'] }}`` and not ``{{ ansible_local['preferences']['general']['XYZ'] }}``. This is because Ansible uses Python's `ConfigParser`_ which passes all option names through the `optionxform`_ method and this method's default implementation converts option names to lower case. 570 571.. _ConfigParser: https://docs.python.org/2/library/configparser.html 572.. _optionxform: https://docs.python.org/2/library/configparser.html#ConfigParser.RawConfigParser.optionxform 573 574You can also use facts.d to execute a script on the remote host, generating dynamic custom facts to the ansible_local namespace. For example, you can generate a list of all users that exist on a remote host as a fact about that host. To generate dynamic custom facts using facts.d: 575 576 #. Write and test a script to generate the JSON data you want. 577 #. Save the script in your facts.d directory. 578 #. Make sure your script has the ``.fact`` file extension. 579 #. Make sure your script is executable by the Ansible connection user. 580 #. Gather facts to execute the script and add the JSON output to ansible_local. 581 582By default, fact gathering runs once at the beginning of each play. If you create a custom fact using facts.d in a playbook, it will be available in the next play that gathers facts. If you want to use it in the same play where you created it, you must explicitly re-run the setup module. For example:: 583 584 - hosts: webservers 585 tasks: 586 587 - name: Create directory for ansible custom facts 588 ansible.builtin.file: 589 state: directory 590 recurse: yes 591 path: /usr/local/etc/ansible/facts.d 592 593 - name: Install custom ipmi fact 594 ansible.builtin.copy: 595 src: ipmi.fact 596 dest: /usr/local/etc/ansible/facts.d 597 598 - name: Re-read facts after adding custom fact 599 ansible.builtin.setup: 600 filter: ansible_local 601 602If you use this pattern frequently, a custom facts module would be more efficient than facts.d. 603 604.. _magic_variables_and_hostvars: 605 606Information about Ansible: magic variables 607========================================== 608 609You can access information about Ansible operations, including the python version being used, the hosts and groups in inventory, and the directories for playbooks and roles, using "magic" variables. Like connection variables, magic variables are :ref:`special_variables`. Magic variable names are reserved - do not set variables with these names. The variable ``environment`` is also reserved. 610 611The most commonly used magic variables are ``hostvars``, ``groups``, ``group_names``, and ``inventory_hostname``. With ``hostvars``, you can access variables defined for any host in the play, at any point in a playbook. You can access Ansible facts using the ``hostvars`` variable too, but only after you have gathered (or cached) facts. 612 613If you want to configure your database server using the value of a 'fact' from another node, or the value of an inventory variable assigned to another node, you can use ``hostvars`` in a template or on an action line:: 614 615 {{ hostvars['test.example.com']['ansible_facts']['distribution'] }} 616 617With ``groups``, a list of all the groups (and hosts) in the inventory, you can enumerate all hosts within a group. For example: 618 619.. code-block:: jinja 620 621 {% for host in groups['app_servers'] %} 622 # something that applies to all app servers. 623 {% endfor %} 624 625You can use ``groups`` and ``hostvars`` together to find all the IP addresses in a group. 626 627.. code-block:: jinja 628 629 {% for host in groups['app_servers'] %} 630 {{ hostvars[host]['ansible_facts']['eth0']['ipv4']['address'] }} 631 {% endfor %} 632 633You can use this approach to point a frontend proxy server to all the hosts in your app servers group, to set up the correct firewall rules between servers, and so on. You must either cache facts or gather facts for those hosts before the task that fills out the template. 634 635With ``group_names``, a list (array) of all the groups the current host is in, you can create templated files that vary based on the group membership (or role) of the host: 636 637.. code-block:: jinja 638 639 {% if 'webserver' in group_names %} 640 # some part of a configuration file that only applies to webservers 641 {% endif %} 642 643You can use the magic variable ``inventory_hostname``, the name of the host as configured in your inventory, as an alternative to ``ansible_hostname`` when fact-gathering is disabled. If you have a long FQDN, you can use ``inventory_hostname_short``, which contains the part up to the first period, without the rest of the domain. 644 645Other useful magic variables refer to the current play or playbook. These vars may be useful for filling out templates with multiple hostnames or for injecting the list into the rules for a load balancer. 646 647``ansible_play_hosts`` is the list of all hosts still active in the current play. 648 649``ansible_play_batch`` is a list of hostnames that are in scope for the current 'batch' of the play. 650 651The batch size is defined by ``serial``, when not set it is equivalent to the whole play (making it the same as ``ansible_play_hosts``). 652 653``ansible_playbook_python`` is the path to the python executable used to invoke the Ansible command line tool. 654 655``inventory_dir`` is the pathname of the directory holding Ansible's inventory host file. 656 657``inventory_file`` is the pathname and the filename pointing to the Ansible's inventory host file. 658 659``playbook_dir`` contains the playbook base directory. 660 661``role_path`` contains the current role's pathname and only works inside a role. 662 663``ansible_check_mode`` is a boolean, set to ``True`` if you run Ansible with ``--check``. 664 665.. _ansible_version: 666 667Ansible version 668--------------- 669 670.. versionadded:: 1.8 671 672To adapt playbook behavior to different versions of Ansible, you can use the variable ``ansible_version``, which has the following structure:: 673 674 "ansible_version": { 675 "full": "2.10.1", 676 "major": 2, 677 "minor": 10, 678 "revision": 1, 679 "string": "2.10.1" 680 } 681