Modern altyap\u0131 y\u00f6netiminde otomasyon, tutarl\u0131l\u0131k ve verimlilik vazge\u00e7ilmez unsurlard\u0131r. Ansible, bu hedeflere ula\u015fmak i\u00e7in geli\u015ftirilmi\u015f, g\u00fc\u00e7l\u00fc ve kullan\u0131m\u0131 kolay bir otomasyon arac\u0131d\u0131r. Sunucular\u0131n ve a\u011f cihazlar\u0131n\u0131n yap\u0131land\u0131rmas\u0131ndan, uygulama da\u011f\u0131t\u0131m\u0131na kadar geni\u015f bir yelpazede g\u00f6revleri otomatikle\u015ftirebilir. Ansible’\u0131n en g\u00fc\u00e7l\u00fc \u00f6zelliklerinden biri de \u015fablonlama (templating) yetene\u011fidir. \u015eablonlar, dinamik ve esnek yap\u0131land\u0131rma dosyalar\u0131 olu\u015fturmam\u0131z\u0131 sa\u011flayarak, farkl\u0131 ortamlar veya sunucular i\u00e7in \u00f6zelle\u015ftirilmi\u015f ayarlar\u0131n otomatik olarak \u00fcretilmesine olanak tan\u0131r.<\/p>\n
Bu makale, Ansible playbook’lar\u0131nda \u015fablonlar\u0131n nas\u0131l olu\u015fturulaca\u011f\u0131n\u0131 ve kullan\u0131laca\u011f\u0131n\u0131 ayr\u0131nt\u0131l\u0131 bir \u015fekilde ele alacakt\u0131r. Jinja2 \u015fablon motorunun temel prensiplerinden ba\u015flayarak, de\u011fi\u015fkenlerin, ko\u015fullar\u0131n ve d\u00f6ng\u00fclerin \u015fablonlar i\u00e7inde nas\u0131l kullan\u0131laca\u011f\u0131n\u0131, pratik uygulama \u00f6rneklerini ve en iyi uygulamalar\u0131 inceleyece\u011fiz. Amac\u0131m\u0131z, okuyucular\u0131n Ansible’\u0131n \u015fablonlama g\u00fcc\u00fcn\u00fc tam olarak anlamalar\u0131n\u0131 ve kendi otomasyon s\u00fcre\u00e7lerinde etkin bir \u015fekilde kullanabilmelerini sa\u011flamakt\u0131r. \u015eablonlar sayesinde, manuel yap\u0131land\u0131rma hatalar\u0131n\u0131 en aza indirebilir, da\u011f\u0131t\u0131m s\u00fcrelerini k\u0131saltabilir ve altyap\u0131 y\u00f6netimini daha g\u00fcvenilir hale getirebiliriz.<\/p>\n
Ansible’\u0131n \u015fablonlama yetene\u011fi, Python tabanl\u0131 pop\u00fcler bir \u015fablon motoru olan Jinja2 taraf\u0131ndan desteklenmektedir. Jinja2, web geli\u015ftirme \u00e7er\u00e7evelerinde (\u00f6rne\u011fin Flask, Django) yayg\u0131n olarak kullan\u0131lmas\u0131n\u0131n yan\u0131 s\u0131ra, yap\u0131land\u0131rma dosyalar\u0131 gibi metin tabanl\u0131 \u00e7\u0131kt\u0131lar\u0131n dinamik olarak olu\u015fturulmas\u0131 i\u00e7in de idealdir. Ansible, Jinja2’yi entegre ederek, playbook’larda tan\u0131mlanan de\u011fi\u015fkenleri, Ansible envanterinden veya toplanan “facts”lerden gelen bilgileri kullanarak \u015fablon dosyalar\u0131n\u0131 i\u015fler ve nihai yap\u0131land\u0131rma dosyas\u0131n\u0131 hedefe kopyalar.<\/p>\n
Jinja2, \u015fablon i\u00e7inde dinamik i\u00e7erik olu\u015fturmak i\u00e7in \u00f6zel s\u00f6zdizimi i\u015faretleyicileri kullan\u0131r:<\/p>\n
* De\u011fi\u015fkenler:<\/strong> De\u011fi\u015fkenlerin de\u011ferlerini \u015fablon i\u00e7inde g\u00f6r\u00fcnt\u00fclemek i\u00e7in \u00e7ift s\u00fcsl\u00fc parantez Ansible, bir \u015fablon dosyas\u0131n\u0131 i\u015flerken, Jinja2 motorunu kullanarak bu s\u00f6zdizimini yorumlar, de\u011fi\u015fkenleri uygun de\u011ferlerle de\u011fi\u015ftirir ve kontrol yap\u0131lar\u0131n\u0131 y\u00fcr\u00fct\u00fcr. Sonu\u00e7 olarak, tamamen statik bir metin dosyas\u0131 elde edilir ve bu dosya hedef sunucuya kopyalan\u0131r. Bu mekanizma, bir kez yaz\u0131lm\u0131\u015f bir \u015fablonun, farkl\u0131 de\u011fi\u015fken setleri ile birden \u00e7ok kez kullan\u0131lmas\u0131na olanak tan\u0131r, b\u00f6ylece kod tekrar\u0131 \u00f6nlenir ve y\u00f6netim kolayla\u015f\u0131r.<\/p>\n Ansible’da \u015fablonlar\u0131 kullanmak, altyap\u0131 otomasyon s\u00fcre\u00e7lerine bir dizi \u00f6nemli avantaj sa\u011flar:<\/p>\n \u015eablonlar, sunucudan sunucuya, ortamdan ortama (geli\u015ftirme, test, \u00fcretim) de\u011fi\u015fen yap\u0131land\u0131rma de\u011ferlerinin otomatik olarak uygulanmas\u0131n\u0131 sa\u011flar. \u00d6rne\u011fin, bir web sunucusunun Ayn\u0131 yap\u0131land\u0131rma dosyas\u0131n\u0131n farkl\u0131 varyasyonlar\u0131n\u0131 manuel olarak olu\u015fturmak yerine, tek bir \u015fablon dosyas\u0131 yaz\u0131l\u0131r ve de\u011fi\u015fkenlerle \u00f6zelle\u015ftirilir. Bu, kod tekrar\u0131n\u0131 ortadan kald\u0131r\u0131r, yap\u0131land\u0131rma dosyalar\u0131n\u0131n bak\u0131m\u0131n\u0131 kolayla\u015ft\u0131r\u0131r ve hata yapma olas\u0131l\u0131\u011f\u0131n\u0131 azalt\u0131r. Bir yap\u0131land\u0131rma kural\u0131 de\u011fi\u015fti\u011finde, sadece \u015fablonu g\u00fcncellemek yeterlidir.<\/p>\n \u015eablonlar, t\u00fcm ortamlar\u0131n\u0131zda (geli\u015ftirme, test, \u00fcretim) yap\u0131land\u0131rma tutarl\u0131l\u0131\u011f\u0131n\u0131 sa\u011flaman\u0131n g\u00fc\u00e7l\u00fc bir yoludur. Ayn\u0131 \u015fablonu kullanarak, her ortam\u0131n kendine \u00f6zg\u00fc de\u011fi\u015fkenlerle beslenmesini sa\u011flayabilir, ancak temel yap\u0131land\u0131rma mant\u0131\u011f\u0131n\u0131n her yerde ayn\u0131 kalmas\u0131n\u0131 garantileyebilirsiniz. Bu, “\u00e7al\u0131\u015ft\u0131 benim makinemde” sorunlar\u0131n\u0131 azalt\u0131r ve da\u011f\u0131t\u0131mlar\u0131n daha g\u00fcvenilir olmas\u0131n\u0131 sa\u011flar.<\/p>\n Veritaban\u0131 \u015fifreleri, API anahtarlar\u0131 gibi hassas bilgiler, \u015fablonlar arac\u0131l\u0131\u011f\u0131yla yap\u0131land\u0131rma dosyalar\u0131na dinamik olarak eklenebilir. Bu bilgiler genellikle Ansible Vault ile \u015fifrelenir ve \u015fablonlar taraf\u0131ndan g\u00fcvenli bir \u015fekilde kullan\u0131l\u0131r. Bu yakla\u015f\u0131m, hassas verilerin a\u00e7\u0131k metin olarak depolanmas\u0131n\u0131 \u00f6nler ve g\u00fcvenlik risklerini azalt\u0131r.<\/p>\n Baz\u0131 uygulamalar\u0131n yap\u0131land\u0131rma dosyalar\u0131 olduk\u00e7a karma\u015f\u0131k olabilir ve bir\u00e7ok farkl\u0131 ayar i\u00e7erebilir. Jinja2’nin d\u00f6ng\u00fc ve ko\u015ful yetenekleri sayesinde, bu karma\u015f\u0131k yap\u0131land\u0131rmalar\u0131 daha y\u00f6netilebilir ve okunabilir bir \u015fekilde \u015fablonlar i\u00e7inde ifade edebiliriz. \u00d6rne\u011fin, birden fazla sanal ana bilgisayar veya g\u00fcvenlik duvar\u0131 kural\u0131 tan\u0131mlamak i\u00e7in d\u00f6ng\u00fcler kullan\u0131labilir.<\/p>\n Ansible’da bir \u015fablon olu\u015fturmak ve kullanmak olduk\u00e7a basittir, ancak birka\u00e7 ad\u0131mdan olu\u015fur.<\/p>\n \u015eablon dosyalar\u0131 genellikle \u00d6rnek olarak, bir Nginx web sunucusu i\u00e7in sanal bir ana bilgisayar yap\u0131land\u0131rma \u015fablonu olu\u015ftural\u0131m: Bu \u00f6rnek \u015fablon: \u015eablon dosyas\u0131n\u0131 olu\u015fturduktan sonra, onu bir Ansible playbook’unda \u00d6rnek bir playbook: Bu playbook’ta: \u015eablonlarda kullan\u0131lan de\u011fi\u015fkenlerin de\u011ferleri farkl\u0131 yerlerden gelebilir:<\/p>\n * Playbook * Komut sat\u0131r\u0131 ( Jinja2, temel de\u011fi\u015fken ikamesinden \u00e7ok daha fazlas\u0131n\u0131 sunar. Geli\u015fmi\u015f filtreler, testler, d\u00f6ng\u00fcler, ko\u015fullar, makrolar ve i\u00e7ermeler (includes) \u015fablonlar\u0131n\u0131z\u0131 daha g\u00fc\u00e7l\u00fc ve esnek hale getirir.<\/p>\n Filtreler, bir de\u011fi\u015fkenin de\u011ferini de\u011fi\u015ftirmek veya d\u00f6n\u00fc\u015ft\u00fcrmek i\u00e7in kullan\u0131l\u0131r. Syntax * Testler, bir de\u011fi\u015fkenin belirli bir ko\u015fulu sa\u011flay\u0131p sa\u011flamad\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in kullan\u0131l\u0131r. Syntax * Jinja2’deki Playbook’ta:<\/p>\n D\u00f6ng\u00fcler i\u00e7inde Makrolar, \u015fablon i\u00e7inde tekrar eden kod bloklar\u0131n\u0131 fonksiyonlar gibi tan\u0131mlaman\u0131za olanak tan\u0131r. Bu, \u015fablonlar\u0131n\u0131z\u0131 daha mod\u00fcler ve okunabilir hale getirir.<\/p>\n Ba\u015fka bir \u015fablonda kullan\u0131m\u0131:<\/p>\n Ana \u015fablonda:<\/p>\n Ansible \u015fablonlar\u0131, \u00e7e\u015fitli ger\u00e7ek d\u00fcnya senaryolar\u0131nda son derece kullan\u0131\u015fl\u0131d\u0131r:<\/p>\n * Nginx\/Apache Sanal Host Yap\u0131land\u0131rmas\u0131:<\/strong> Farkl\u0131 Ansible \u015fablonlar\u0131n\u0131 etkin ve s\u00fcrd\u00fcr\u00fclebilir bir \u015fekilde kullanmak i\u00e7in baz\u0131 en iyi uygulamalar\u0131 takip etmek \u00f6nemlidir:<\/p>\n * \u015eablonlar\u0131 D\u00fczenli Tutma:<\/strong> T\u00fcm \u015fablon dosyalar\u0131n\u0131z\u0131 playbook’unuzla ayn\u0131 d\u00fczeyde veya ayr\u0131 bir \u015eablonlarla \u00e7al\u0131\u015f\u0131rken kar\u015f\u0131la\u015f\u0131labilecek baz\u0131 yayg\u0131n sorunlar ve bunlar\u0131n \u00e7\u00f6z\u00fcmleri:<\/p>\n * De\u011fi\u015fken Bulunamad\u0131 Hatas\u0131 ( Ansible’da \u015fablonlar, altyap\u0131 otomasyonunun kalbinde yer alan g\u00fc\u00e7l\u00fc ve esnek bir \u00f6zelliktir. Jinja2 \u015fablon motorunu kullanarak, dinamik yap\u0131land\u0131rma dosyalar\u0131 olu\u015fturabilir, kod tekrar\u0131n\u0131 ortadan kald\u0131rabilir, ortamlar aras\u0131nda tutarl\u0131l\u0131k sa\u011flayabilir ve karma\u015f\u0131k yap\u0131land\u0131rma g\u00f6revlerini basitle\u015ftirebiliriz. Bu makalede ele ald\u0131\u011f\u0131m\u0131z temel ve geli\u015fmi\u015f teknikler, Jinja2’nin de\u011fi\u015fkenler, ko\u015fullar, d\u00f6ng\u00fcler, filtreler ve makrolar gibi yeteneklerini kullanarak otomasyon s\u00fcre\u00e7lerinizi bir \u00fcst seviyeye ta\u015f\u0131man\u0131za yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n \u015eablonlar\u0131 etkili bir \u015fekilde kullanarak, Ansible playbook’lar\u0131n\u0131z daha mod\u00fcler, okunabilir ve s\u00fcrd\u00fcr\u00fclebilir hale gelir. En iyi uygulamalar\u0131 takip etmek ve yayg\u0131n sorunlar\u0131n \u00fcstesinden gelmek, otomasyon projelerinizin ba\u015far\u0131s\u0131 i\u00e7in kritik \u00f6neme sahiptir. Ansible’\u0131n \u015fablonlama g\u00fcc\u00fcnden tam olarak yararlanarak, altyap\u0131 y\u00f6netim s\u00fcre\u00e7lerinizi daha verimli, daha g\u00fcvenilir ve daha tutarl\u0131 hale getirebilirsiniz. Unutmay\u0131n, iyi tasarlanm\u0131\u015f bir \u015fablon, say\u0131s\u0131z manuel yap\u0131land\u0131rma hatas\u0131n\u0131 ve zaman kayb\u0131n\u0131 \u00f6nleyebilir.<\/p>\n","protected":false},"excerpt":{"rendered":"Ansible Playbook’larda \u015eablonlar\u0131 (Templates) Olu\u015fturma ve Kullanma\nGiri\u015f\nModern altyap\u0131 y\u00f6netiminde otomasyon, tutarl\u0131l\u0131k ve verimlilik vaz","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1],"tags":[],"class_list":{"0":"post-36514","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-genel","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\n{{ variable }}<\/code> kullan\u0131l\u0131r. \u00d6rne\u011fin, {{ server_name }}<\/code> ifadesi, server_name<\/code> adl\u0131 de\u011fi\u015fkenin de\u011ferini ekrana yazd\u0131r\u0131r.
\n* Kontrol Yap\u0131lar\u0131:<\/strong> Mant\u0131k (ko\u015fullar, d\u00f6ng\u00fcler) uygulamak i\u00e7in y\u00fczde i\u015faretleri ve s\u00fcsl\u00fc parantezler {% control_statement %}<\/code> kullan\u0131l\u0131r.
\n * Ko\u015fullar (If\/Else):<\/strong> {% if condition %}<\/code> … {% elif another_condition %}<\/code> … {% else %}<\/code> … {% endif %}<\/code>
\n * D\u00f6ng\u00fcler (For):<\/strong> {% for item in list %}<\/code> … {% endfor %}<\/code>
\n* Yorumlar:<\/strong> \u015eablon i\u00e7inde a\u00e7\u0131klama eklemek i\u00e7in #<\/code> i\u015faretleri ve s\u00fcsl\u00fc parantezler {# comment #}<\/code> kullan\u0131l\u0131r. Bu yorumlar, i\u015flenmi\u015f \u00e7\u0131kt\u0131da yer almaz.
\n* Filtreler:<\/strong> De\u011fi\u015fkenlerin de\u011ferlerini de\u011fi\u015ftirmek veya bi\u00e7imlendirmek i\u00e7in dikey \u00e7izgi |<\/code> ile filtreler uygulan\u0131r. \u00d6rne\u011fin, {{ variable | upper }}<\/code> de\u011fi\u015fkenin de\u011ferini b\u00fcy\u00fck harflere d\u00f6n\u00fc\u015ft\u00fcr\u00fcr.<\/p>\nAnsible’da Template Kullan\u0131m\u0131n\u0131n Avantajlar\u0131<\/h3>\n
Dinamik Konfig\u00fcrasyon<\/h4>\n
server_name<\/code> veya listen_port<\/code> gibi ayarlar\u0131, her sunucu veya ortam i\u00e7in farkl\u0131 olabilir. \u015eablonlar sayesinde, bu de\u011ferleri dinamik olarak playbook’lardan veya envanterden alarak do\u011fru yap\u0131land\u0131rma dosyas\u0131n\u0131 olu\u015fturabiliriz.<\/p>\nKod Tekrar\u0131n\u0131 \u00d6nleme (DRY – Don’t Repeat Yourself)<\/h4>\n
Ortamlar Aras\u0131 Tutarl\u0131l\u0131k<\/h4>\n
Hassas Bilgilerin Y\u00f6netimi<\/h4>\n
Karma\u015f\u0131k Yap\u0131land\u0131rmalar\u0131n Basitle\u015ftirilmesi<\/h4>\n
Template Olu\u015fturma ve Kullanma Ad\u0131mlar\u0131<\/h3>\n
Ad\u0131m 1: Template Dosyas\u0131n\u0131 Olu\u015fturma (.j2 uzant\u0131s\u0131)<\/h4>\n
.j2<\/code> uzant\u0131s\u0131yla adland\u0131r\u0131l\u0131r (Jinja2’den gelir), ancak bu zorunlu de\u011fildir. Bu uzant\u0131, dosyan\u0131n bir Jinja2 \u015fablonu oldu\u011funu belirtmek i\u00e7in bir konvansiyondur. \u015eablon dosyalar\u0131n\u0131z\u0131 genellikle playbook’lar\u0131n\u0131zla ayn\u0131 dizinde veya playbook’un alt\u0131ndaki \u00f6zel bir templates\/<\/code> dizininde saklamak iyi bir uygulamad\u0131r.<\/p>\nnginx.conf.j2<\/code><\/p>\n# nginx.conf.j2\nserver {\n listen {{ http_port | default(80) }};\n listen {{ https_port | default(443) }} ssl;\n\n server_name {{ domain_name }};\n\n ssl_certificate \/etc\/nginx\/ssl\/{{ domain_name }}.crt;\n ssl_certificate_key \/etc\/nginx\/ssl\/{{ domain_name }}.key;\n\n root \/var\/www\/{{ domain_name }}\/html;\n index index.html index.htm;\n\n location \/ {\n try_files $uri $uri\/ =404;\n }\n\n {% if enable_redirect_to_www %}\n if ($host !~* ^www\\.{{ domain_name }}$) {\n rewrite ^(.*)$ https:\/\/www.{{ domain_name }}$1 permanent;\n }\n {% endif %}\n\n {% if custom_locations is defined and custom_locations %}\n # Custom locations\n {% for location in custom_locations %}\n location {{ location.path }} {\n proxy_pass {{ location.proxy_target }};\n proxy_set_header Host $host;\n proxy_set_header X-Real-IP $remote_addr;\n }\n {% endfor %}\n {% endif %}\n\n error_log \/var\/log\/nginx\/{{ domain_name }}_error.log warn;\n access_log \/var\/log\/nginx\/{{ domain_name }}_access.log combined;\n}\n\nAnsible taraf\u0131ndan y\u00f6netilen {{ ansible_hostname }} \u00fczerinde.<\/h2>\n
OS: {{ ansible_distribution }} {{ ansible_distribution_version }}<\/code><\/pre>\n<\/h2>\n
\n* http_port<\/code>, https_port<\/code>, domain_name<\/code> gibi de\u011fi\u015fkenler kullan\u0131r.
\n* default<\/code> filtresi ile portlara varsay\u0131lan de\u011ferler atar.
\n* if<\/code> ko\u015fulu ile enable_redirect_to_www<\/code> de\u011fi\u015fkenine g\u00f6re www y\u00f6nlendirmesi ekler.
\n* if<\/code> ve for<\/code> d\u00f6ng\u00fcleri ile custom_locations<\/code> listesindeki \u00f6zel konumlar\u0131 dinamik olarak ekler.
\n* Ansible’\u0131n otomatik olarak toplad\u0131\u011f\u0131 ansible_hostname<\/code>, ansible_distribution<\/code>, ansible_distribution_version<\/code> gibi “facts”leri kullan\u0131r.<\/p>\nAd\u0131m 2: Ansible Playbook’ta Template Kullan\u0131m\u0131<\/h4>\n
template<\/code> mod\u00fcl\u00fc ile kullanabiliriz. template<\/code> mod\u00fcl\u00fc, belirtilen \u015fablon dosyas\u0131n\u0131 i\u015fler ve sonucu hedef sunucudaki belirtilen yola kopyalar.<\/p>\ndeploy_nginx.yml<\/code><\/p>\n---\n- name: Nginx Web Sunucusu Kurulumu ve Yap\u0131land\u0131rmas\u0131\n hosts: webservers\n become: yes # Y\u00f6netici haklar\u0131 ile \u00e7al\u0131\u015ft\u0131r\n\n vars:\n http_port: 80\n https_port: 443\n domain_name: example.com\n enable_redirect_to_www: true\n custom_locations:\n - path: \/api\/\n proxy_target: http:\/\/backend-service:8080\/\n - path: \/admin\/\n proxy_target: http:\/\/admin-panel:9000\/\n\n tasks:\n - name: Nginx paketini y\u00fckle\n ansible.builtin.apt:\n name: nginx\n state: present\n when: ansible_os_family == \"Debian\"\n\n - name: Nginx yap\u0131land\u0131rma dizinini olu\u015ftur\n ansible.builtin.file:\n path: \/etc\/nginx\/sites-available\n state: directory\n mode: '0755'\n\n - name: SSL dizinini olu\u015ftur\n ansible.builtin.file:\n path: \/etc\/nginx\/ssl\n state: directory\n mode: '0700'\n\n # \u00d6rnek SSL sertifikas\u0131 ve anahtar\u0131 olu\u015fturma (ger\u00e7ek uygulamada sertifika y\u00f6neticisi kullan\u0131n)\n - name: SSL sertifika ve anahtar\u0131 olu\u015ftur (sadece \u00f6rnek)\n community.crypto.openssl_csr:\n path: \"\/etc\/nginx\/ssl\/{{ domain_name }}.csr\"\n privatekey_path: \"\/etc\/nginx\/ssl\/{{ domain_name }}.key\"\n common_name: \"{{ domain_name }}\"\n organization_name: \"Example Corp\"\n args:\n creates: \"\/etc\/nginx\/ssl\/{{ domain_name }}.key\" # Sadece dosya yoksa olu\u015ftur\n when: not ansible.builtin.stat(path=\"\/etc\/nginx\/ssl\/{{ domain_name }}.key\").stat.exists\n\n - name: Self-signed SSL sertifikas\u0131 olu\u015ftur (sadece \u00f6rnek)\n community.crypto.x509_certificate:\n path: \"\/etc\/nginx\/ssl\/{{ domain_name }}.crt\"\n privatekey_path: \"\/etc\/nginx\/ssl\/{{ domain_name }}.key\"\n csr_path: \"\/etc\/nginx\/ssl\/{{ domain_name }}.csr\"\n provider: selfsigned\n args:\n creates: \"\/etc\/nginx\/ssl\/{{ domain_name }}.crt\"\n when: not ansible.builtin.stat(path=\"\/etc\/nginx\/ssl\/{{ domain_name }}.crt\").stat.exists\n\n - name: Nginx yap\u0131land\u0131rma dosyas\u0131n\u0131 \u015fablondan olu\u015ftur\n ansible.builtin.template:\n src: nginx.conf.j2 # Kaynak \u015fablon dosyas\u0131\n dest: \"\/etc\/nginx\/sites-available\/{{ domain_name }}.conf\" # Hedef dosya yolu\n owner: root\n group: root\n mode: '0644'\n notify: Nginx'i yeniden ba\u015flat\n\n - name: Nginx yap\u0131land\u0131rmas\u0131n\u0131 etkinle\u015ftir (symlink olu\u015ftur)\n ansible.builtin.file:\n src: \"\/etc\/nginx\/sites-available\/{{ domain_name }}.conf\"\n dest: \"\/etc\/nginx\/sites-enabled\/{{ domain_name }}.conf\"\n state: link\n notify: Nginx'i yeniden ba\u015flat\n\n - name: Varsay\u0131lan Nginx yap\u0131land\u0131rmas\u0131n\u0131 devre d\u0131\u015f\u0131 b\u0131rak\n ansible.builtin.file:\n path: \/etc\/nginx\/sites-enabled\/default\n state: absent\n notify: Nginx'i yeniden ba\u015flat\n\n - name: Nginx servisini ba\u015flat ve ba\u015flang\u0131\u00e7ta etkinle\u015ftir\n ansible.builtin.systemd:\n name: nginx\n state: started\n enabled: yes\n\n handlers:\n - name: Nginx'i yeniden ba\u015flat\n ansible.builtin.systemd:\n name: nginx\n state: restarted<\/code><\/pre>\n
\n* vars<\/code> blo\u011funda \u015fablonda kullan\u0131lacak de\u011fi\u015fkenler tan\u0131mlanm\u0131\u015ft\u0131r.
\n* ansible.builtin.template<\/code> mod\u00fcl\u00fc, nginx.conf.j2<\/code> \u015fablonunu i\u015fler ve dest<\/code> parametresinde belirtilen yola kopyalar.
\n* owner<\/code>, group<\/code>, mode<\/code> parametreleri kopyalanan dosyan\u0131n izinlerini ve sahipli\u011fini ayarlar.
\n* notify<\/code> ifadesi, yap\u0131land\u0131rma dosyas\u0131 de\u011fi\u015fti\u011finde Nginx servisinin yeniden ba\u015flat\u0131lmas\u0131n\u0131 sa\u011flayan bir handler<\/code> tetikler.<\/p>\nAd\u0131m 3: De\u011fi\u015fkenlerin Y\u00f6netimi<\/h4>\n
vars<\/code> blo\u011fu:<\/strong> Yukar\u0131daki \u00f6rnekte oldu\u011fu gibi, playbook’un kendisinde tan\u0131mlanan de\u011fi\u015fkenler.
\n* Envanter dosyalar\u0131 (group_vars<\/code> ve host_vars<\/code>):<\/strong> Daha yap\u0131land\u0131r\u0131lm\u0131\u015f ve ortam bazl\u0131 de\u011fi\u015fkenler i\u00e7in inventory\/group_vars\/webservers.yml<\/code> veya inventory\/host_vars\/webserver1.example.com.yml<\/code> gibi dosyalar kullan\u0131labilir.
\n * inventory\/group_vars\/webservers.yml<\/code>:<\/p>\ndomain_name: example.com\n http_port: 80\n https_port: 443\n enable_redirect_to_www: true\n custom_locations:\n - path: \/api\/\n proxy_target: http:\/\/backend-service:8080\/<\/code><\/pre>\n--extra-vars<\/code> veya -e<\/code>):<\/strong> Ge\u00e7ici veya tek seferlik de\u011fi\u015fkenler i\u00e7in ansible-playbook deploy_nginx.yml -e \"domain_name=newdomain.com\"<\/code>
\n* Ansible Facts:<\/strong> Ansible taraf\u0131ndan hedef sunucular hakk\u0131nda otomatik olarak toplanan bilgiler (ansible_hostname<\/code>, ansible_os_family<\/code>, ansible_default_ipv4.address<\/code> vb.).
\n* set_fact<\/code> mod\u00fcl\u00fc:<\/strong> Playbook i\u00e7inde dinamik olarak yeni de\u011fi\u015fkenler olu\u015fturmak i\u00e7in kullan\u0131l\u0131r.
\n* Ansible Vault:<\/strong> Hassas verileri (\u015fifreler, API anahtarlar\u0131) \u015fifrelemek ve g\u00fcvenli bir \u015fekilde \u015fablonlarda kullanmak i\u00e7in.<\/p>\nGeli\u015fmi\u015f Template Teknikleri<\/h3>\n
Jinja2 Filtreleri<\/h4>\n
{{ variable | filter_name(arg1, arg2) }}<\/code> \u015feklindedir.<\/p>\ndefault(value)<\/code>: De\u011fi\u015fken tan\u0131ml\u0131 de\u011filse veya bo\u015fsa varsay\u0131lan bir de\u011fer sa\u011flar. (\u00d6rnek \u015fablonda kullan\u0131ld\u0131)
\n* upper<\/code>, lower<\/code>, capitalize<\/code>, title<\/code>, trim<\/code>: Metin dizelerini bi\u00e7imlendirme.
\n * {{ \"hello world\" | upper }}<\/code> -> HELLO WORLD<\/code>
\n* split(separator)<\/code>, join(separator)<\/code>: Dizeleri b\u00f6lme veya birle\u015ftirme.
\n * {{ my_list | join(', ') }}<\/code>
\n* to_nice_json<\/code>, to_yaml<\/code>: Python veri yap\u0131lar\u0131n\u0131 JSON veya YAML format\u0131na d\u00f6n\u00fc\u015ft\u00fcrme. \u00d6zellikle yap\u0131land\u0131rma dosyalar\u0131na karma\u015f\u0131k veri yap\u0131lar\u0131 yazarken kullan\u0131\u015fl\u0131d\u0131r.
\n * {{ my_dict | to_nice_json(indent=2) }}<\/code>
\n* ipaddr('address\/net')<\/code>: IP adresleri ile ilgili i\u015flemler (\u00f6rne\u011fin, bir IP adresinin belirli bir alt a\u011fda olup olmad\u0131\u011f\u0131n\u0131 kontrol etme).
\n * {{ '192.168.1.10' | ipaddr('192.168.1.0\/24') }}<\/code> -> True<\/code>
\n* hash('md5')<\/code>, sha1<\/code>, sha256<\/code>: Dize de\u011ferlerinin hash’ini olu\u015fturma. G\u00fcvenlik ve b\u00fct\u00fcnl\u00fck kontrolleri i\u00e7in.<\/p>\nJinja2 Testleri<\/h4>\n
{% if variable is test_name %}<\/code> \u015feklindedir.<\/p>\nis defined<\/code>, is undefined<\/code>: De\u011fi\u015fkenin tan\u0131ml\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol eder. (\u00d6rnek \u015fablonda custom_locations is defined<\/code> kullan\u0131ld\u0131)
\n* is none<\/code>: De\u011fi\u015fkenin None<\/code> olup olmad\u0131\u011f\u0131n\u0131 kontrol eder.
\n* is divisibleby(number)<\/code>: Say\u0131n\u0131n belirli bir say\u0131ya b\u00f6l\u00fcn\u00fcp b\u00f6l\u00fcnmedi\u011fini kontrol eder.
\n* is string<\/code>, is number<\/code>, is boolean<\/code>: De\u011fi\u015fkenin tipini kontrol eder.
\n* is iterable<\/code>: De\u011fi\u015fkenin bir d\u00f6ng\u00fcde kullan\u0131l\u0131p kullan\u0131lamayaca\u011f\u0131n\u0131 kontrol eder.<\/p>\nD\u00f6ng\u00fcler (Loops)<\/h4>\n
for<\/code> d\u00f6ng\u00fcleri, listeler veya s\u00f6zl\u00fckler (dictionaries) \u00fczerinde tekrarlayan bloklar olu\u015fturmak i\u00e7in kullan\u0131l\u0131r.<\/p>\n# users.conf.j2\n{% for user in system_users %}\nUser {{ user.name }} {{ user.uid }} {{ user.gid }}\n Comment \"{{ user.comment | default('System User') }}\"\n {% if user.home_dir is defined %}\n HomeDirectory {{ user.home_dir }}\n {% endif %}\n{% endfor %}<\/code><\/pre>\nvars:\n system_users:\n - name: alice\n uid: 1001\n gid: 1001\n comment: \"Alice User\"\n - name: bob\n uid: 1002\n gid: 1002\n home_dir: \/home\/bob<\/code><\/pre>\nloop.index<\/code>, loop.index0<\/code>, loop.first<\/code>, loop.last<\/code>, loop.length<\/code> gibi \u00f6zel de\u011fi\u015fkenler de kullan\u0131labilir.<\/p>\nKo\u015fullar (Conditionals)<\/h4>\n
if<\/code>, elif<\/code>, else<\/code> bloklar\u0131, \u015fablon i\u00e7inde mant\u0131ksal kararlar almak i\u00e7in kullan\u0131l\u0131r. (\u00d6rnek Nginx \u015fablonunda enable_redirect_to_www<\/code> ve custom_locations<\/code> i\u00e7in kullan\u0131ld\u0131).<\/p>\n{% if environment == \"production\" %}\nLogLevel info\n{% elif environment == \"development\" %}\nLogLevel debug\n{% else %}\nLogLevel warn\n{% endif %}<\/code><\/pre>\nMakrolar (Macros)<\/h4>\n
macros.j2<\/code> dosyas\u0131:<\/p>\n{% macro define_user(username, uid, gid) %}\nuseradd -u {{ uid }} -g {{ gid }} {{ username }}\n{% endmacro %}<\/code><\/pre>\n{% import 'macros.j2' as my_macros %}\n\n{{ my_macros.define_user('john', 1003, 1003) }}\n{{ my_macros.define_user('jane', 1004, 1004) }}<\/code><\/pre>\nIncludes<\/h4>\n
include<\/code> direktifi, bir \u015fablon dosyas\u0131n\u0131n i\u00e7eri\u011fini ba\u015fka bir \u015fablon dosyas\u0131na dahil etmenizi sa\u011flar. Bu, b\u00fcy\u00fck \u015fablonlar\u0131 daha k\u00fc\u00e7\u00fck, y\u00f6netilebilir par\u00e7alara b\u00f6lmek i\u00e7in kullan\u0131\u015fl\u0131d\u0131r.<\/p>\nheader.j2<\/code>:<\/p>\n# Bu dosya {{ ansible_hostname }} i\u00e7in otomatik olarak olu\u015fturuldu.\nTarih: {{ ansible_date_time.iso8601_micro }}<\/code><\/pre>\n<\/h2>\n
{% include 'header.j2' %}\n\nserver {\n listen 80;\n server_name {{ domain_name }};\n # ...\n}<\/code><\/pre>\nPratik Uygulama \u00d6rnekleri<\/h3>\n
server_name<\/code>, root<\/code> dizinleri, SSL sertifikalar\u0131 ve proxy ayarlar\u0131 ile birden fazla sanal host yap\u0131land\u0131rmas\u0131n\u0131 otomatikle\u015ftirmek.
\n* Veritaban\u0131 Ba\u011flant\u0131 Ayarlar\u0131:<\/strong> Uygulama sunucular\u0131nda veritaban\u0131 ba\u011flant\u0131 dizelerini (kullan\u0131c\u0131 ad\u0131, \u015fifre, host, port) dinamik olarak olu\u015fturmak. Hassas veriler i\u00e7in Ansible Vault ile birlikte kullanmak.
\n* Ortama \u00d6zel Uygulama Yap\u0131land\u0131rma Dosyalar\u0131:<\/strong> Geli\u015ftirme, test ve \u00fcretim ortamlar\u0131 i\u00e7in farkl\u0131 API anahtarlar\u0131, g\u00fcnl\u00fck seviyeleri veya hizmet u\u00e7 noktalar\u0131 i\u00e7eren uygulama yap\u0131land\u0131rma dosyalar\u0131 (application.properties<\/code>, .env<\/code>, config.json<\/code>).
\n* CRON \u0130\u015fleri Tan\u0131mlama:<\/strong> Farkl\u0131 komutlar, zamanlamalar ve kullan\u0131c\u0131lar i\u00e7in dinamik CRON i\u015fleri olu\u015fturmak.
\n* G\u00fcvenlik Duvar\u0131 Kurallar\u0131:<\/strong> Belirli IP adresleri, portlar veya protokoller i\u00e7in g\u00fcvenlik duvar\u0131 kurallar\u0131n\u0131 (iptables, firewalld) \u015fablonlar arac\u0131l\u0131\u011f\u0131yla dinamik olarak olu\u015fturmak.
\n* DNS Kay\u0131tlar\u0131:<\/strong> DNS sunucular\u0131nda (Bind, PowerDNS) A, CNAME, MX gibi kay\u0131tlar\u0131 otomatik olarak eklemek.<\/p>\nEn \u0130yi Uygulamalar (Best Practices)<\/h3>\n
templates\/<\/code> dizini alt\u0131nda saklay\u0131n. Bu, projenin yap\u0131s\u0131n\u0131 d\u00fczenli tutar.
\n* De\u011fi\u015fken Adland\u0131rma Kurallar\u0131na Uyma:<\/strong> De\u011fi\u015fkenlerinizi anlaml\u0131 ve tutarl\u0131 bir \u015fekilde adland\u0131r\u0131n. \u00d6rne\u011fin, http_port<\/code> yerine nginx_http_port<\/code> gibi daha spesifik isimler kullanabilirsiniz, \u00f6zellikle farkl\u0131 rollerde ayn\u0131 isimde de\u011fi\u015fkenler varsa.
\n* \u015eablonlar\u0131 Basit ve Okunabilir Tutma:<\/strong> \u015eablonlar, genellikle yap\u0131land\u0131rma dosyalar\u0131n\u0131n iskeletini sa\u011flamal\u0131 ve \u00e7ok karma\u015f\u0131k mant\u0131k i\u00e7ermemelidir. A\u015f\u0131r\u0131 karma\u015f\u0131k mant\u0131\u011f\u0131 (\u00f6rne\u011fin, yo\u011fun veri i\u015fleme) Jinja2 yerine Python’da veya Ansible playbook’un di\u011fer g\u00f6revlerinde (\u00f6rne\u011fin set_fact<\/code> ile de\u011fi\u015fkenleri \u00f6nceden i\u015fleme) uygulamay\u0131 d\u00fc\u015f\u00fcn\u00fcn.
\n* \u015eablonlar\u0131 Test Etme:<\/strong> ansible-playbook --syntax-check<\/code> komutu, playbook’unuzdaki Jinja2 s\u00f6zdizimi hatalar\u0131n\u0131 yakalaman\u0131za yard\u0131mc\u0131 olabilir. Ayr\u0131ca, \u015fablonun beklenen \u00e7\u0131kt\u0131y\u0131 \u00fcretip \u00fcretmedi\u011fini g\u00f6rmek i\u00e7in “dry run” modunda (--check<\/code>) playbook’u \u00e7al\u0131\u015ft\u0131rabilirsiniz.
\n* Hassas Veriler \u0130\u00e7in Ansible Vault Kullanma:<\/strong> \u015eifreler, API anahtarlar\u0131 gibi hassas bilgileri asla a\u00e7\u0131k metin olarak \u015fablonlarda veya de\u011fi\u015fken dosyalar\u0131nda saklamay\u0131n. Bunun yerine Ansible Vault’u kullanarak bu verileri \u015fifreleyin ve \u015fablonlar\u0131n\u0131zda g\u00fcvenli bir \u015fekilde kullan\u0131n.
\n* Yorumlar\u0131 Etkili Kullanma:<\/strong> \u015eablonlar\u0131n\u0131z\u0131n i\u00e7inde karma\u015f\u0131k mant\u0131k veya belirli bir ama\u00e7 i\u00e7in yap\u0131lm\u0131\u015f b\u00f6l\u00fcmleri a\u00e7\u0131klamak i\u00e7in Jinja2 yorumlar\u0131n\u0131 {# comment #}<\/code> kullan\u0131n.
\n* Tekrar Kullan\u0131labilirli\u011fi D\u00fc\u015f\u00fcnme:<\/strong> \u015eablonlar\u0131, farkl\u0131 senaryolarda veya projelerde tekrar kullan\u0131labilecek \u015fekilde genel ve parametrik hale getirmeye \u00e7al\u0131\u015f\u0131n.<\/p>\nS\u0131k Kar\u015f\u0131la\u015f\u0131lan Sorunlar ve \u00c7\u00f6z\u00fcmleri<\/h3>\n
Undefined variable<\/code>):<\/strong> Bu hata, \u015fablonda kullan\u0131lan bir de\u011fi\u015fkenin playbook’ta veya envanterde tan\u0131mlanmam\u0131\u015f olmas\u0131 durumunda ortaya \u00e7\u0131kar.
\n * \u00c7\u00f6z\u00fcm:<\/strong> De\u011fi\u015fkenin t\u00fcm olas\u0131 kaynaklarda (playbook vars, group_vars, host_vars, extra-vars) do\u011fru \u015fekilde tan\u0131mland\u0131\u011f\u0131ndan emin olun. default<\/code> filtresini kullanarak de\u011fi\u015fkenin tan\u0131ml\u0131 olmamas\u0131 durumunda bir varsay\u0131lan de\u011fer sa\u011flayabilirsiniz.
\n* S\u00f6zdizimi Hatalar\u0131 (Jinja2 SyntaxError):<\/strong> Jinja2 s\u00f6zdizimi kurallar\u0131na uymayan bir ifade kullan\u0131ld\u0131\u011f\u0131nda bu hata olu\u015fur.
\n * \u00c7\u00f6z\u00fcm:<\/strong> Jinja2 s\u00f6zdizimini dikkatlice kontrol edin (\u00f6rne\u011fin, {{ }}<\/code> ve {% %}<\/code> i\u015faretlerinin do\u011fru kullan\u0131m\u0131, etiketlerin kapanmas\u0131). Hata mesaj\u0131 genellikle hatan\u0131n hangi sat\u0131rda oldu\u011funu g\u00f6sterir.
\n* Dosya \u0130zinleri ve Sahipli\u011fi Sorunlar\u0131:<\/strong> Kopyalanan yap\u0131land\u0131rma dosyas\u0131n\u0131n hedef sunucuda yanl\u0131\u015f izinlere veya sahipli\u011fe sahip olmas\u0131.
\n * \u00c7\u00f6z\u00fcm:<\/strong> template<\/code> mod\u00fcl\u00fcnde owner<\/code>, group<\/code> ve mode<\/code> parametrelerini do\u011fru \u015fekilde ayarlay\u0131n. Genellikle yap\u0131land\u0131rma dosyalar\u0131 i\u00e7in root:root<\/code> sahipli\u011fi ve 0644<\/code> veya 0600<\/code> gibi izinler kullan\u0131l\u0131r.
\n* Servis Yeniden Ba\u015flatmama:<\/strong> Yap\u0131land\u0131rma dosyas\u0131 g\u00fcncellenmesine ra\u011fmen ilgili servisin (Nginx, Apache vb.) yeniden ba\u015flat\u0131lmamas\u0131.
\n * \u00c7\u00f6z\u00fcm:<\/strong> template<\/code> g\u00f6revinin notify<\/code> parametresini kullanarak ilgili handler<\/code>‘\u0131 tetikledi\u011finizden emin olun. Handler’\u0131n ad\u0131n\u0131n notify<\/code> parametresindeki adla tam olarak e\u015fle\u015fti\u011finden emin olun.
\n* Karma\u015f\u0131k Mant\u0131k Hatalar\u0131:<\/strong> \u015eablonda \u00e7ok karma\u015f\u0131k Jinja2 mant\u0131\u011f\u0131 kullan\u0131ld\u0131\u011f\u0131nda, beklenen \u00e7\u0131kt\u0131y\u0131 alamamak.
\n * \u00c7\u00f6z\u00fcm:<\/strong> \u015eablonu daha k\u00fc\u00e7\u00fck, daha basit par\u00e7alara ay\u0131r\u0131n. Karma\u015f\u0131k veri i\u015fleme veya ko\u015fullu mant\u0131\u011f\u0131 Jinja2 i\u00e7inde yapmak yerine, playbook’un kendisinde set_fact<\/code> veya di\u011fer mod\u00fcllerle de\u011fi\u015fkenleri \u00f6nceden haz\u0131rlay\u0131n.<\/p>\nSonu\u00e7<\/h3>\n