{"id":1359,"date":"2021-05-26T17:18:03","date_gmt":"2021-05-26T17:18:03","guid":{"rendered":"https:\/\/www.nicktailor.com\/?p=1359"},"modified":"2021-05-27T07:17:26","modified_gmt":"2021-05-27T07:17:26","slug":"how-to-add-vm-tags-and-custom-attributes-with-anisblevmware","status":"publish","type":"post","link":"https:\/\/nicktailor.com\/tech-blog\/how-to-add-vm-tags-and-custom-attributes-with-anisblevmware\/","title":{"rendered":"How to add VM-Tags and Custom attributes with Anisble(VMware)"},"content":{"rendered":"

So whether your using cloud or doing in house deploys. Tagging is a used a lot especially in cloud type environments. Which we will cover in later posts. <\/strong><\/p>\n

So a common reason to tag your vm is wanting to have the creation date and the type of server or environment its using, handy for backup solutions & other auditables.<\/strong><\/p>\n

.<\/span><\/span><\/p>\n

Pre-requisites: Assumed.<\/strong><\/p>\n

\n
\n
\u2022<\/span>\u00a0<\/span>Ansible 2.9 installed and configured \u2013<\/span><\/strong><\/div>\n<\/div>\n
\n
\u2022<\/span>\u00a0<\/span>Vmware<\/span> Community modules configured<\/span><\/strong><\/div>\n<\/div>\n
\n
\u2022<\/span>\u00a0<\/span>Vmware<\/span> group variables previously defined for <\/span>vmware<\/span> deployments(Is helpful)<\/span><\/strong><\/div>\n

.<\/span><\/span><\/p>\n<\/div>\n<\/div>\n

Step by Step:<\/strong><\/p>\n

\n
\n
\n

1.<\/span>Create a roles directory inside \/etc\/ansible\/roles<\/strong><\/p>\n<\/div>\n

\n
\n
a.<\/span>mkdir -p \/etc\/ansible\/roles\/custom-tags-attributes-vmware\/tasks<\/em><\/strong><\/div>\n<\/div>\n
\n
\n

b.<\/span>mkdir -p \/etc\/ansible\/roles\/ custom-tags-attributes-vmware\/defaults<\/em><\/strong><\/p>\n

 <\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n

2.<\/span>Now you want to create a task for the snapshots.<\/strong><\/p>\n<\/div>\n

\n
\n
c.<\/span>Inside \/etc\/ansible\/roles\/custom-tags-attributes-vmware\/tasks\/<\/em><\/strong><\/div>\n<\/div>\n
\n
\n

d.<\/span>Create a file called main.yml<\/em><\/strong><\/p>\n

 <\/p>\n<\/div>\n

<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
3.<\/span>Add the following code and save the file<\/strong>\u00a0<\/strong><\/div>\n
<\/div>\n<\/div>\n<\/div>\n

Note: Okay for the custom attributes to work you need to get the <\/span>MOID, <\/span>UUID<\/span> & Folder<\/span> of the <\/span>vm<\/span> by using the <\/span>vm<\/span> name.<\/span> So we need to gather facts about the <\/span>vm<\/span> and the set those facts as variables that we can pass to the next tasks.<\/span><\/strong><\/p>\n

 <\/p>\n

– name: get list of facts<\/h2>\n

\u00a0\u00a0vmware_guest_facts:<\/h2>\n

hostname: “{{ vcenter_host }}”<\/h2>\n

username: “{{ vcenter_username }}”<\/h2>\n

password: “{{ vcenter_password }}”<\/h2>\n

name: “{{ inventory_hostname }}”<\/h2>\n

\u00a0\u00a0\u00a0\u00a0datacenter: “{{ vcenter_dc }}”<\/h2>\n

\u00a0\u00a0\u00a0\u00a0validate_certs: False<\/h2>\n

\u00a0\u00a0delegate_to: localhost<\/h2>\n

\u00a0\u00a0ignore_errors: true<\/h2>\n

register: vm_facts<\/strong><\/h2>\n

 <\/p>\n

Note: So when we use the <\/em><\/span>vmware_guest_facts<\/em><\/span> module to gather the facts about the <\/em><\/span>v<\/em><\/span>m<\/em><\/span> by register the facts to a variable \u201c<\/em><\/span>vm_facts<\/em><\/span>\u201d<\/em><\/span>, which when you run the playbook with –<\/em><\/span>vvvv<\/em><\/span> will spit out the <\/em><\/span>facst<\/em><\/span> you can pass as indicated below.<\/em><\/span><\/strong>.<\/span><\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span> “<\/span>hw_folder<\/span>“: “\/<\/span>SysUnix<\/span>\/Test<\/span>ing<\/span>“,<\/span><\/strong><\/p>\n

“<\/span>hw_guest_full_name<\/span>“: “Red Hat Enterprise Linux 7 (64-bit)”,<\/span><\/p>\n

“<\/span>hw_guest_ha_state<\/span>“: true,<\/span><\/p>\n

“<\/span>hw_guest_id<\/span>“: “rhel7_64Guest”,<\/span><\/p>\n

“<\/span>hw_interfaces<\/span>“: [<\/span><\/p>\n

“eth0”<\/span><\/p>\n

],<\/span><\/p>\n

“<\/span>hw_is_template<\/span>“: false,<\/span><\/p>\n

“<\/span>hw_memtotal_mb<\/span>“: 2048,<\/span><\/p>\n

“<\/span>hw_name<\/span>“: “v-sits-test4”,<\/span><\/p>\n

“<\/span>hw_power_status<\/span>“: “<\/span>poweredOn<\/span>“,<\/span><\/p>\n

“<\/span>hw_processor_count<\/span>“: 2,<\/span><\/p>\n

“<\/span>hw_product_uuid<\/span>“: “4226d4e1-6be8-9447-5ced-b037075e2ffd”,<\/span><\/p>\n

“<\/span>hw_version<\/span>“: “vmx-11”,<\/span><\/p>\n

“<\/span>instance_uuid<\/span>“: “50263518-c95b-c3be-5c77-4e1ea69ec295”,<\/span><\/strong><\/p>\n

“ipv4”: “1<\/span>92.168.1.29<\/span>“,<\/span><\/p>\n

“ipv6”: null,<\/span><\/p>\n

“<\/span>module_hw<\/span>“: true,<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span>“<\/span>moid<\/span>“: “vm-296678”,<\/span><\/strong><\/p>\n

“snapshots”: [],<\/span><\/p>\n

“<\/span>vimref<\/span>“: “vim.VirtualMachine:vm-296678”,<\/span><\/p>\n

“<\/span>vnc<\/span>“: {}<\/span><\/p>\n

.<\/span><\/span><\/p>\n

.<\/span><\/span>Note: Now that we have the <\/em><\/span>UUID<\/em><\/span>, MOID, & Folder. <\/em><\/span>We now want to create static variables for UUID, MOID, & folder by using the previous variable we registered as \u201c<\/em><\/span>vm_facts<\/em><\/span>\u201d, and we want to set them as static variables by setting them as facts we can past to the tasks after. As indicated below. Again setting facts is the same as defining variables in bash. Just ansible way to do it.<\/em><\/span><\/strong><\/p>\n

 <\/p>\n

– set_fact:<\/strong><\/h2>\n

\u00a0\u00a0\u00a0\u00a0vm_uuid: “{{ vm_facts.instance.instance_uuid }}”<\/strong><\/h2>\n

– set_fact:<\/strong><\/h2>\n

\u00a0\u00a0\u00a0\u00a0moid: “{{ vm_facts.instance.moid }}”<\/strong><\/h2>\n

– set_fact:<\/strong><\/h2>\n

\u00a0\u00a0\u00a0\u00a0vm_folder: “{{ vm_facts.instance.hw_folder }}”<\/strong><\/h2>\n

 <\/p>\n

Note<\/em><\/span>: <\/em>Now want to use the ansible server date and pass that as a variable so you don\u2019t have to input the date as manual value each time you deploy a new host. So we want to grab the date and setup a static fact and then pass it as its own variable. Like we did above\u2026<\/em><\/span><\/strong><\/p>\n

– name: Get Date<\/h2>\n

shell: date +%Y-%m-%d<\/h2>\n

register: date<\/strong><\/h2>\n

\u00a0\u00a0delegate_to: localhost<\/h2>\n

 <\/p>\n

Note: We use shell module to get the date in the format we want, then register the result as the variable {{ date }}. We then set a static fact of the result and create another variable called date with using the result from the above.<\/em><\/span><\/strong><\/p>\n

– set_fact:<\/strong><\/h2>\n

\u00a0\u00a0\u00a0\u00a0date: “{{ date.stdout }}”<\/strong><\/h2>\n

 <\/p>\n

Note: We now want to pass all the fact to the \u201c<\/em><\/span>vmware_guest_custom_attributes<\/em><\/span>\u201d <\/em>module <\/em><\/span>UUID<\/em><\/span>, <\/em><\/span>MOID<\/em><\/span>, <\/em><\/span>DATE<\/em><\/span>, and <\/em><\/span>Folder <\/em><\/span>indicated as below.<\/em><\/span><\/strong><\/p>\n

– name: Add multiple virtual machine custom attributes<\/h2>\n

\u00a0\u00a0vmware_guest_custom_attributes:<\/h2>\n

hostname: “{{ vcenter_host }}”<\/h2>\n

username: “{{ vcenter_username }}”<\/h2>\n

password: “{{ vcenter_password }}”<\/h2>\n

name: “{{ inventory_hostname }}”<\/h2>\n

\u00a0\u00a0\u00a0\u00a0datacenter: “{{ vcenter_dc }}”<\/h2>\n

\u00a0\u00a0\u00a0 folder: “{{ vm_folder }}”<\/strong><\/h2>\n

\u00a0\u00a0\u00a0\u00a0uuid: “{{ vm_facts.instance.instance_uuid }}”<\/strong><\/h2>\n

\u00a0\u00a0\u00a0\u00a0moid: “{{ vm_facts.instance.moid }}”<\/strong><\/h2>\n

state: present<\/h2>\n

\u00a0\u00a0\u00a0\u00a0validate_certs: False<\/h2>\n

\u00a0\u00a0\u00a0\u00a0use_instance_uuid: True<\/h2>\n

attributes:<\/h2>\n

– name: Creation Date<\/h2>\n

value: “{{ date }}”\u00a0\u00a0\u00a0<\/strong><\/h2>\n

# – name: MyAttribute2 – Note: You can add additional attributes if you wish<\/span><\/strong><\/h2>\n

# value: test2 – Note: You can add additional attributes if you wish<\/span><\/strong><\/h2>\n

\u00a0\u00a0delegate_to: localhost<\/h2>\n

register: attributes<\/h2>\n

 <\/p>\n

Note: Okay so depending on which module you use, some require you to gather facts about the <\/em><\/span>vmware<\/em><\/span> categories. This is <\/em><\/span>just <\/em><\/span>incase<\/em><\/span> you need the <\/em><\/span>cateogory_id<\/em><\/span> which is usually <\/em><\/span>derived<\/em><\/span> from using a REST API in json or other method. The \u201c<\/em><\/span>community.vmware.vmware_category_facts<\/em><\/span>\u201d<\/em>will<\/em><\/span> be able to pull the info and then you can pass it <\/em><\/span>as a variable or a static value<\/em><\/span>. IF YOU NEED, however this is NOT needed. If you use the <\/em><\/span>\u201c<\/em><\/span>vmware_tag_manager<\/em><\/span>\u201d module”
\n<\/em><\/span><\/strong><\/h2>\n

\u00a0<\/em><\/span><\/strong><\/p>\n

– name: Gather facts about tag categories<\/span><\/strong><\/h2>\n

\u00a0\u00a0<\/span>community.vmware.vmware_category_facts<\/span>:<\/span><\/strong><\/h2>\n

hostname: “{{ <\/span>vcenter_host<\/span> }}”<\/span><\/strong><\/h2>\n

username: “{{ <\/span>vcenter_username<\/span> }}”<\/span><\/strong><\/h2>\n

password: “{{ <\/span>vcenter_password<\/span> }}”<\/span><\/strong><\/h2>\n

\u00a0\u00a0\u00a0\u00a0<\/span>validate_certs<\/span>: no<\/span><\/strong><\/h2>\n

\u00a0\u00a0<\/span>delegate_to<\/span>: localhost<\/span><\/strong><\/h2>\n

register: <\/span>all_tag_category_facts<\/span><\/strong><\/h2>\n

.<\/span><\/span><\/p>\n

ok: [v-sits-test4] => {<\/span><\/p>\n

“changed”: false,<\/span><\/p>\n

“invocation”: {<\/span><\/p>\n

“<\/span>module_args<\/span>“: {<\/span><\/p>\n

“hostname”: “<\/span>vmware.nicktailor.com<\/span>“,<\/span><\/p>\n

“password”: “VALUE_SPECIFIED_IN_NO_LOG_PARAMETER”,<\/span><\/p>\n

“port”: 443,<\/span><\/p>\n

“protocol”: “https”,<\/span><\/p>\n

“username”: “<\/span>admin<\/span>“,<\/span><\/p>\n

“<\/span>validate_certs<\/span>“: false<\/span><\/p>\n

}<\/span><\/p>\n

},<\/span><\/p>\n

“<\/span>tag_category_facts<\/span>“: [<\/span><\/p>\n

{<\/span><\/p>\n

“<\/span>category_associable_types<\/span>“: [<\/span><\/p>\n

“<\/span>VirtualMachine<\/span>“<\/span><\/p>\n

],<\/span><\/p>\n

“<\/span>category_cardinality<\/span>“: “SINGLE”,<\/span><\/p>\n

“<\/span>category_description<\/span>“: “VM Type – Clone, <\/span>Decomm<\/span>, Dev, Prod, SRM, SLM, Template or Test”,<\/span><\/strong><\/p>\n

“<\/span>category_id<\/span>“: “urn:vmomi:InventoryServiceCategory:f10<\/span>2<\/span>4eb<\/span>4<\/span>-d7d<\/span>4<\/span>-49fe-9<\/span>7<\/span>25-4dcba39fbe<\/span>3<\/span>b:GLOBAL”,<\/span><\/strong><\/p>\n

“<\/span>category_name<\/span>“: “<\/span>VMType<\/span>“,<\/span><\/p>\n

“<\/span>category_used_by<\/span>“: []<\/span><\/p>\n

},<\/span><\/p>\n

{<\/span><\/p>\n

“<\/span>category_associable_types<\/span>“: [<\/span><\/p>\n

“<\/span>VirtualMachine<\/span>“<\/span><\/p>\n

],<\/span><\/p>\n

“<\/span>category_cardinality<\/span>“: “SINGLE”,<\/span><\/p>\n

“<\/span>category_description<\/span>“: “Team or Department”,<\/span><\/p>\n

“<\/span>category_id<\/span>“: “urn:vmomi:InventoryServiceCategory:<\/span>88<\/span>8a0877-<\/span>5<\/span>335-4<\/span>4<\/span>77-9347-6d8de5b3e<\/span>60e<\/span>:GLOBAL”,<\/span><\/strong><\/p>\n

“<\/span>category_name<\/span>“: “Team\/Dept”,<\/span><\/p>\n

“<\/span>category_used_by<\/span>“: []<\/span><\/p>\n

}<\/span><\/p>\n

]<\/span><\/p>\n

}<\/span><\/p>\n

.<\/span><\/span><\/p>\n

.<\/span><\/span><\/p>\n

Note: Now that we <\/em><\/span>want to create the tag for the <\/em><\/span>vm<\/em><\/span> using the \u201c<\/em><\/span>\u201c<\/em><\/span>vmware_tag_manager<\/em><\/span>\u201d <\/em><\/span>module<\/em><\/span>. The only variable that is passed from outside the defaults at the <\/em><\/span>inventory_hostname<\/em><\/span> level \u201c<\/em><\/span>host_var<\/em><\/span>\/nicktest1\u201d<\/em><\/span> is the {{ <\/em><\/span>vm_tag<\/em><\/span> }} Make sure you have this defined for the role to work properly.<\/em><\/span><\/strong><\/h2>\n

 <\/p>\n

– name: Add tags to a virtual machine<\/h2>\n

\u00a0\u00a0vmware_tag_manager:<\/h2>\n

hostname: ‘{{ vcenter_host }}’<\/h2>\n

username: ‘{{ vcenter_username }}’<\/h2>\n

password: ‘{{ vcenter_password }}’<\/h2>\n

\u00a0\u00a0\u00a0\u00a0validate_certs: no<\/h2>\n

\u00a0\u00a0\u00a0\u00a0tag_names:<\/h2>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0– “{{ vm_tag }}” \u2013 passed at the host_var<\/span>\/nicktest1<\/span><\/strong><\/h2>\n

\u00a0\u00a0\u00a0\u00a0object_name: “{{ inventory_hostname }}”<\/h2>\n

\u00a0\u00a0\u00a0\u00a0object_type: VirtualMachine<\/h2>\n

state: present<\/h2>\n

\u00a0\u00a0delegate_to: localhost<\/h2>\n

 <\/p>\n

\n
\n
4.<\/span>Save the file<\/strong><\/div>\n<\/div>\n
\n
5.<\/span>You can either have group_vars<\/span> set up for individual datacenters, but for now just define the variables under \/etc\/ansible\/roles\/<\/span>custom-tags-attributes-<\/span>vmware<\/span>\/defaults<\/span><\/strong><\/div>\n

.<\/span><\/span><\/p>\n

Note: You will likely have a <\/em><\/span>group_var<\/em><\/span> from you <\/em><\/span>vmdeploy<\/em><\/span> role that you can use for here.<\/em><\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

\n
\n
e.<\/span>Create a file called main.yml and the following variables<\/strong><\/div>\n

vcenter_username<\/span>: admin<\/span><\/strong><\/p>\n

vcenter_password<\/span>: should be vault encrypted variable<\/span><\/strong><\/p>\n

vcenter_host<\/span>: vmware.nicktailor.com<\/span><\/strong><\/p>\n

vcenter_dc<\/span>: London<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

.<\/span><\/span><\/p>\n<\/div>\n

\n
f.<\/span>Save the file<\/span><\/strong><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/p>\n

\n
\n
\u2022<\/span>\u00a0<\/span>Note: Ensure your host \u201cnicktest1\u201d is listed in your inventory host file. <\/span><\/strong>
\n\/etc\/ansible\/inventory\/TEST\/hosts<\/em><\/span><\/strong><\/div>\n<\/div>\n
\n
\u2022<\/span>\u00a0<\/span>Note: Make sure your \u201c<\/span>host_var<\/span>\/nicktest1″\u00a0<\/span><\/span>has the \u201cvm_tag<\/span>: {{ value }}\u201d defined<\/span><\/span><\/strong><\/div>\n
<\/div>\n<\/div>\n<\/div>\n

 <\/p>\n

Run your playbook: from <\/span>\/etc\/ansible<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

\n
\n
1.<\/span>ansible-playbook –<\/span>i<\/span> inventory\/TEST\/hosts <\/span>justremovevmsnap.yml<\/span> –ask-vault-pass –limit=’nicktest1′ <\/span><\/strong><\/div>\n

.<\/span><\/span><\/p>\n

Playbook log:<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

[root@ansible-server]# ansible-playbook –<\/span>i<\/span> inventory\/TEST\/hosts <\/span>justcustomattrib.yml<\/span> –ask-vault-pass –limit=’v-sits-test4′<\/span><\/strong><\/p>\n

Vault password:<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

PLAY [all] **********************************************************************************************************************************<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

TASK [custom-tags-attributes-<\/span>vmware<\/span> : get list of facts] ************************************************************************************<\/span><\/strong><\/p>\n

[DEPRECATION WARNING]: The ‘<\/span>vmware_guest_facts<\/span>‘ module has been renamed to ‘<\/span>vmware_guest_info<\/span>‘. This feature will be removed in version<\/span><\/strong><\/p>\n

2.13. Deprecation warnings can be disabled by setting <\/span>deprecation_warnings<\/span>=False in <\/span>ansible.cfg<\/span>.<\/span><\/strong><\/p>\n

ok: [v-sits-test4]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

TASK [custom-tags-attributes-<\/span>vmware<\/span> : <\/span>set_fact<\/span>] *********************************************************************************************<\/span><\/strong><\/p>\n

ok: [v-sits-test4]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

TASK [custom-tags-attributes-<\/span>vmware<\/span> : <\/span>set_fact<\/span>] *********************************************************************************************<\/span><\/strong><\/p>\n

ok: [v-sits-test4]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

TASK [custom-tags-attributes-<\/span>vmware<\/span> : <\/span>set_fact<\/span>] *********************************************************************************************<\/span><\/strong><\/p>\n

ok: [v-sits-test4]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

TASK [custom-tags-attributes-<\/span>vmware<\/span> : Get Date] *********************************************************************************************<\/span><\/strong><\/p>\n

changed: [v-sits-test4]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

TASK [custom-tags-attributes-<\/span>vmware<\/span> : <\/span>set_fact<\/span>] *********************************************************************************************<\/span><\/strong><\/p>\n

ok: [v-sits-test4]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

TASK [custom-tags-attributes-<\/span>vmware<\/span> : Add multiple virtual machine custom attributes] *******************************************************<\/span><\/strong><\/p>\n

ok: [v-sits-test4]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

TASK [custom-tags-attributes-<\/span>vmware<\/span> : Gather facts about tag categories] ********************************************************************<\/span><\/strong><\/p>\n

ok: [v-sits-test4]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

TASK [custom-tags-attributes-<\/span>vmware<\/span> : Add tags to a virtual machine] ************************************************************************<\/span><\/strong><\/p>\n

ok: [v-sits-test4]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

PLAY RECAP **********************************************************************************************************************************<\/span><\/strong><\/p>\n

v-sits-test4 : ok=9 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0<\/span><\/strong><\/p>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

So whether your using cloud or doing in house deploys. Tagging is a used a lot especially in cloud type environments. Which we will cover in later posts. So a common reason to tag your vm is wanting to have the creation date and the type of server or environment its using, handy for backup solutions & other auditables. .Read More …<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[51,129],"tags":[],"class_list":["post-1359","post","type-post","status-publish","format-standard","hentry","category-ansible","category-vmware"],"_links":{"self":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/1359","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/comments?post=1359"}],"version-history":[{"count":28,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/1359\/revisions"}],"predecessor-version":[{"id":1388,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/1359\/revisions\/1388"}],"wp:attachment":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/media?parent=1359"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/categories?post=1359"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/tags?post=1359"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}