Ansible, otomasyon d\u00fcnyas\u0131nda basitli\u011fi, arac\u0131s\u0131z mimarisi ve g\u00fc\u00e7l\u00fc yetenekleriyle \u00f6ne \u00e7\u0131kan bir ara\u00e7t\u0131r. Ancak otomasyon, her zaman d\u00fcz bir yol izlemez; \u00e7o\u011fu zaman farkl\u0131 durumlara, sistem yap\u0131land\u0131rmalar\u0131na veya kullan\u0131c\u0131 tercihlerine g\u00f6re farkl\u0131 eylemlerin ger\u00e7ekle\u015ftirilmesi gerekir. \u0130\u015fte bu noktada “ko\u015fullu ifadeler” (conditionals) devreye girer. Ansible playbook’lar\u0131n\u0131z\u0131n dinamik, esnek ve ak\u0131ll\u0131 olmas\u0131n\u0131 sa\u011flayan ko\u015fullu ifadeler, belirli bir ko\u015fulun do\u011fru olup olmad\u0131\u011f\u0131na ba\u011fl\u0131 olarak g\u00f6revleri, rolleri veya di\u011fer otomasyon ad\u0131mlar\u0131n\u0131 y\u00fcr\u00fctmenize olanak tan\u0131r.<\/p>\n
Bu makalede, Ansible playbook’lar\u0131nda ko\u015fullu ifadelerin nas\u0131l kullan\u0131laca\u011f\u0131n\u0131, farkl\u0131 senaryolara y\u00f6nelik \u00e7e\u015fitli teknikleri ve en iyi uygulamalar\u0131 derinlemesine inceleyece\u011fiz.<\/p>\n
Otomasyonun temel prensiplerinden biri, “idempotency” yani bir i\u015flemin birden \u00e7ok kez tekrarland\u0131\u011f\u0131nda ayn\u0131 sonucu vermesidir. Ko\u015fullu ifadeler, bu prensibi desteklemede kritik bir rol oynar. \u00d6rne\u011fin, bir paketi yaln\u0131zca y\u00fckl\u00fc de\u011filse kurmak, bir hizmeti yaln\u0131zca \u00e7al\u0131\u015fm\u0131yorsa ba\u015flatmak veya bir yap\u0131land\u0131rma dosyas\u0131n\u0131 yaln\u0131zca belirli bir i\u015fletim sisteminde da\u011f\u0131tmak gibi senaryolarda ko\u015fullu ifadeler vazge\u00e7ilmezdir.<\/p>\n
Ko\u015fullu ifadeler sayesinde: Ansible’da ko\u015fullu ifadelerin en temel ve yayg\u0131n kullan\u0131m \u015fekli Bir g\u00f6revin yaln\u0131zca belirli bir ko\u015ful alt\u0131nda \u00e7al\u0131\u015fmas\u0131n\u0131 istiyorsan\u0131z, Yukar\u0131daki \u00f6rnekte, Karma\u015f\u0131k senaryolarda birden fazla ko\u015fulu birle\u015ftirmek gerekebilir. Bunun i\u00e7in Parantez kullanarak ko\u015fullar\u0131n de\u011ferlendirme s\u0131ras\u0131n\u0131 belirleyebilirsiniz:<\/p>\n Bir de\u011fi\u015fkenin tan\u0131ml\u0131 olup olmad\u0131\u011f\u0131n\u0131 veya bo\u015f olup olmad\u0131\u011f\u0131n\u0131 kontrol etmek s\u0131k\u00e7a kar\u015f\u0131la\u015f\u0131lan bir durumdur. Bu, \u00f6zellikle iste\u011fe ba\u011fl\u0131 de\u011fi\u015fkenler veya dinamik olarak olu\u015fturulan de\u011fi\u015fkenlerle \u00e7al\u0131\u015f\u0131rken \u00f6nemlidir.<\/p>\n Bir listenin belirli bir \u00f6\u011feyi i\u00e7erip i\u00e7ermedi\u011fini kontrol etmek i\u00e7in Ansible, D\u00f6ng\u00fclerle birlikte Yukar\u0131daki \u00f6rnekte, sadece B\u00fcy\u00fck ve mod\u00fcler playbook’larda, belirli rolleri veya g\u00f6rev dosyalar\u0131n\u0131 ko\u015fullu olarak dahil etmek isteyebilirsiniz. Bu, playbook’lar\u0131n\u0131z\u0131n daha d\u00fczenli ve y\u00f6netilebilir olmas\u0131n\u0131 sa\u011flar.<\/p>\n Not:<\/strong> Bazen bir de\u011fi\u015fkenin de\u011ferini belirli bir ko\u015fula g\u00f6re ayarlaman\u0131z gerekebilir. Bunu Daha k\u0131sa bir yol i\u00e7in Ansible, bir g\u00f6revin ba\u015far\u0131l\u0131 m\u0131 yoksa ba\u015far\u0131s\u0131z m\u0131 oldu\u011funu veya bir de\u011fi\u015fikli\u011fe neden olup olmad\u0131\u011f\u0131n\u0131 varsay\u0131lan olarak belirli \u00e7\u0131k\u0131\u015f kodlar\u0131na veya durumlar\u0131na g\u00f6re belirler. Ancak bu davran\u0131\u015f\u0131 * * Ansible facts, y\u00f6netilen host’lar hakk\u0131nda toplanan dinamik verilerdir (i\u015fletim sistemi, a\u011f aray\u00fczleri, bellek, disk vb.). Bu bilgiler, playbook’lar\u0131n\u0131zda ko\u015fullu ifadeler i\u00e7in temel bir kaynakt\u0131r. Yayg\u0131n kullan\u0131lan fact’ler ve \u00f6rnekleri: Kendi \u00f6zel fact’lerinizi de olu\u015fturabilir ve bunlar\u0131 ko\u015fullu ifadelerde kullanabilirsiniz. Bunun i\u00e7in Ansible, yap\u0131land\u0131rma dosyalar\u0131n\u0131 dinamik olarak olu\u015fturmak i\u00e7in Jinja2 \u015fablon motorunu kullan\u0131r. Jinja2’nin kendi i\u00e7inde de ko\u015fullu ifadeler bulunur ( Playbook’ta bu \u015fablonu kullan\u0131rken:<\/p>\n Burada, Jinja2 ayr\u0131ca listeler \u00fczerinde ko\u015fullu filtreleme yapmak i\u00e7in Bu \u00f6rnekte, * Okunabilirlik ve Sadelik:<\/strong> Karma\u015f\u0131k * Performans:<\/strong> M\u00fcmk\u00fcnse, ko\u015fullar\u0131 daha \u00fcst seviyelerde (\u00f6rne\u011fin, play veya rol d\u00fczeyinde) de\u011ferlendirerek gereksiz g\u00f6revlerin veya rol dahil etmelerinin \u00f6n\u00fcne ge\u00e7in. * Tan\u0131mlanmam\u0131\u015f De\u011fi\u015fkenler:<\/strong> Bir de\u011fi\u015fken tan\u0131ml\u0131 de\u011filse ve Ansible playbook’lar\u0131nda ko\u015fullu ifadeler, otomasyonunuzu daha dinamik, esnek ve ak\u0131ll\u0131 hale getiren temel bir ara\u00e7t\u0131r. Bu makalede ele al\u0131nan teknikleri ve en iyi uygulamalar\u0131 benimseyerek, daha sa\u011flam, bak\u0131m\u0131 kolay ve hataya dayan\u0131kl\u0131 Ansible playbook’lar\u0131 olu\u015fturabilirsiniz. Unutmay\u0131n, iyi yaz\u0131lm\u0131\u015f ko\u015fullu ifadeler, otomasyonunuzun sadece \u00e7al\u0131\u015fmas\u0131n\u0131 de\u011fil, ayn\u0131 zamanda do\u011fru, verimli ve \u00f6ng\u00f6r\u00fclebilir bir \u015fekilde \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar. Otomasyon yolculu\u011funuzda ko\u015fullu ifadelerin g\u00fcc\u00fcn\u00fc ke\u015ffetmeye devam edin!
\n* Esneklik:<\/strong> Playbook’lar\u0131n\u0131z farkl\u0131 ortamlar ve sistemler aras\u0131nda daha esnek hale gelir.
\n* Verimlilik:<\/strong> Gereksiz g\u00f6revlerin \u00e7al\u0131\u015fmas\u0131n\u0131 engelleyerek otomasyon s\u00fcre\u00e7lerinizi h\u0131zland\u0131r\u0131r.
\n* Hata Tolerans\u0131:<\/strong> Hatal\u0131 veya istenmeyen durumlar\u0131n olu\u015fmas\u0131n\u0131 \u00f6nlemeye yard\u0131mc\u0131 olur.
\n* Dinamik Davran\u0131\u015f:<\/strong> Sistemden toplanan bilgilere (facts) veya harici verilere g\u00f6re playbook’lar\u0131n\u0131z\u0131n davran\u0131\u015f\u0131n\u0131 de\u011fi\u015ftirebilirsiniz.<\/p>\nTemel Ko\u015fullu Yap\u0131:
when<\/code> Anahtar Kelimesi<\/h3>\nwhen<\/code> anahtar kelimesidir. when<\/code> ifadesi, bir g\u00f6revin (task), blo\u011fun (block) veya hatta bir rol\u00fcn (role) yaln\u0131zca belirli bir ko\u015ful do\u011fruysa y\u00fcr\u00fct\u00fclmesini sa\u011flar.<\/p>\nwhen<\/code> ifadesi, Jinja2 \u015fablon motorunu kullanarak de\u011ferlendirilen bir Python ifadesi al\u0131r. Bu ifade, True<\/code> veya False<\/code> olarak sonu\u00e7lanmal\u0131d\u0131r.<\/p>\nG\u00f6rev D\u00fczeyinde
when<\/code> Kullan\u0131m\u0131<\/h4>\nwhen<\/code> ifadesini do\u011frudan g\u00f6reve ekleyebilirsiniz:<\/p>\n- name: Apache web sunucusunu kur\n ansible.builtin.apt:\n name: apache2\n state: present\n when: ansible_os_family == \"Debian\"\n\n- name: Nginx web sunucusunu kur\n ansible.builtin.yum:\n name: nginx\n state: present\n when: ansible_os_family == \"RedHat\"<\/code><\/pre>\nansible_os_family<\/code> bir Ansible fact’idir ve \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131 sistemin i\u015fletim sistemi ailesini belirtir. Debian tabanl\u0131 bir sistemde Apache, RedHat tabanl\u0131 bir sistemde ise Nginx kurulacakt\u0131r.<\/p>\nBirden Fazla Ko\u015ful Kullan\u0131m\u0131:
and<\/code>, or<\/code>, not<\/code><\/h4>\nand<\/code> (ve), or<\/code> (veya) ve not<\/code> (de\u011fil) mant\u0131ksal operat\u00f6rlerini kullanabilirsiniz:<\/p>\n- name: Apache'yi yaln\u0131zca Debian ve \u00fcretim ortam\u0131nda ba\u015flat\n ansible.builtin.service:\n name: apache2\n state: started\n when: ansible_os_family == \"Debian\" and environment == \"production\"\n\n- name: Uygulamay\u0131 yaln\u0131zca test veya geli\u015ftirme ortam\u0131nda da\u011f\u0131t\n ansible.builtin.git:\n repo: 'https:\/\/github.com\/my\/app.git'\n dest: \/var\/www\/my_app\n when: environment == \"test\" or environment == \"development\"\n\n- name: Yaln\u0131zca k\u00f6k kullan\u0131c\u0131 de\u011filse bir dosya olu\u015ftur\n ansible.builtin.file:\n path: \/tmp\/user_file.txt\n state: touch\n when: ansible_user_id != \"root\"<\/code><\/pre>\n- name: Geli\u015fmi\u015f ko\u015fullu g\u00f6rev\n ansible.builtin.debug:\n msg: \"Bu g\u00f6rev \u00e7al\u0131\u015f\u0131yor!\"\n when: (ansible_os_family == \"Debian\" and ansible_distribution_major_version == \"10\") or environment == \"staging\"<\/code><\/pre>\nDe\u011fi\u015fken Varl\u0131\u011f\u0131n\u0131 Kontrol Etme:
is defined<\/code>, is not defined<\/code><\/h4>\n- name: Yaln\u0131zca 'my_variable' tan\u0131ml\u0131ysa bir mesaj g\u00f6ster\n ansible.builtin.debug:\n msg: \"my_variable de\u011feri: {{ my_variable }}\"\n when: my_variable is defined\n\n- name: Yaln\u0131zca 'my_list' tan\u0131ml\u0131 de\u011filse bir liste olu\u015ftur\n ansible.builtin.set_fact:\n my_list: []\n when: my_list is not defined\n\n- name: Yaln\u0131zca 'my_string' bo\u015f de\u011filse bir dosya olu\u015ftur\n ansible.builtin.file:\n path: \/tmp\/my_file.txt\n state: touch\n when: my_string is not none and my_string | length > 0 # veya my_string | default('') | length > 0<\/code><\/pre>\nis none<\/code> ve is not none<\/code> de kullan\u0131labilir. Bir de\u011fi\u015fken tan\u0131ml\u0131 de\u011filse, Jinja2 bunu none<\/code> olarak kabul eder.<\/p>\nListe \u0130\u00e7eriklerini Kontrol Etme<\/h4>\n
in<\/code> operat\u00f6r\u00fcn\u00fc kullanabilirsiniz:<\/p>\n- name: \"webserver\" grubundaki host'lar i\u00e7in Apache'yi kur\n ansible.builtin.apt:\n name: apache2\n state: present\n when: \"'webserver' in group_names\" # group_names, host'un dahil oldu\u011fu gruplar\u0131n listesidir\n\n- name: \"Ubuntu\" veya \"Debian\" ise bir g\u00f6rev \u00e7al\u0131\u015ft\u0131r\n ansible.builtin.debug:\n msg: \"Bu bir Debian tabanl\u0131 sistemdir.\"\n when: ansible_distribution in ['Ubuntu', 'Debian']<\/code><\/pre>\nGeli\u015fmi\u015f Ko\u015fullu Senaryolar<\/h3>\n
when<\/code> anahtar kelimesinin \u00f6tesinde daha karma\u015f\u0131k ko\u015fullu mant\u0131klar i\u00e7in \u00e7e\u015fitli mekanizmalar sunar.<\/p>\nKo\u015fullu D\u00f6ng\u00fcler (Conditionals with Loops)<\/h4>\n
when<\/code> kullanmak, bir listedeki \u00f6\u011feleri belirli ko\u015fullara g\u00f6re filtrelemenizi veya her bir \u00f6\u011fe i\u00e7in farkl\u0131 eylemler ger\u00e7ekle\u015ftirmenizi sa\u011flar.<\/p>\n- name: Belirli kullan\u0131c\u0131lar\u0131 olu\u015ftur\n ansible.builtin.user:\n name: \"{{ item.name }}\"\n state: present\n groups: \"{{ item.groups | default('') }}\"\n loop:\n - { name: 'john', groups: 'dev' }\n - { name: 'jane', groups: 'ops' }\n - { name: 'bob', groups: 'dev' }\n when: item.groups == 'dev'<\/code><\/pre>\ngroups<\/code> de\u011feri ‘dev’ olan kullan\u0131c\u0131lar olu\u015fturulacakt\u0131r.<\/p>\nKo\u015fullu Rol ve G\u00f6rev Dahil Etme<\/h4>\n
include_role<\/code>, import_role<\/code>, include_tasks<\/code>, import_tasks<\/code> mod\u00fclleri ile when<\/code> kullanabilirsiniz.<\/p>\n- name: Apache rol\u00fcn\u00fc yaln\u0131zca Debian tabanl\u0131 sistemlerde dahil et\n ansible.builtin.include_role:\n name: apache\n when: ansible_os_family == \"Debian\"\n\n- name: Nginx rol\u00fcn\u00fc yaln\u0131zca RedHat tabanl\u0131 sistemlerde dahil et\n ansible.builtin.include_role:\n name: nginx\n when: ansible_os_family == \"RedHat\"\n\n- name: Geli\u015ftirme ortam\u0131 g\u00f6revlerini dahil et\n ansible.builtin.include_tasks: develop_tasks.yml\n when: environment == \"development\"<\/code><\/pre>\nimport_role<\/code> ve import_tasks<\/code> statik dahil etmelerdir ve when<\/code> ko\u015fullar\u0131 playbook ayr\u0131\u015ft\u0131r\u0131l\u0131rken de\u011ferlendirilir. include_role<\/code> ve include_tasks<\/code> dinamik dahil etmelerdir ve when<\/code> ko\u015fullar\u0131 \u00e7al\u0131\u015fma zaman\u0131nda de\u011ferlendirilir. \u00c7o\u011fu durumda include_*<\/code> tercih edilir, \u00e7\u00fcnk\u00fc daha esnektir.<\/p>\nKo\u015fullu De\u011fi\u015fken Tan\u0131mlama<\/h4>\n
set_fact<\/code> mod\u00fcl\u00fcyle veya Jinja2 filtreleriyle yapabilirsiniz.<\/p>\n- name: Uygulama portunu ortama g\u00f6re ayarla\n ansible.builtin.set_fact:\n app_port: 8080\n when: environment == \"production\"\n\n- name: Uygulama portunu geli\u015ftirme i\u00e7in ayarla\n ansible.builtin.set_fact:\n app_port: 8000\n when: environment == \"development\"\n\n- name: Varsay\u0131lan portu ayarla (e\u011fer \u00f6ncekiler \u00e7al\u0131\u015fmad\u0131ysa)\n ansible.builtin.set_fact:\n app_port: 9000\n when: app_port is not defined # veya else gibi d\u00fc\u015f\u00fcnebilirsiniz<\/code><\/pre>\ndefault<\/code> filtresi veya ternary<\/code> filtresi kullan\u0131labilir:<\/p>\n- name: Portu tek bir de\u011fi\u015fkende tan\u0131mla\n ansible.builtin.set_fact:\n app_port: \"{{ 8080 if environment == 'production' else 8000 }}\"<\/code><\/pre>\nKo\u015fullu Hata Y\u00f6netimi:
failed_when<\/code> ve changed_when<\/code><\/h4>\nfailed_when<\/code> ve changed_when<\/code> ile \u00f6zelle\u015ftirebilirsiniz.<\/p>\nfailed_when<\/code><\/strong>: Bir g\u00f6revin \u00e7\u0131k\u0131\u015f\u0131na veya durumuna bakarak g\u00f6revin ne zaman ba\u015far\u0131s\u0131z say\u0131laca\u011f\u0131n\u0131 tan\u0131mlar. \u00d6zellikle bir komut veya betik mod\u00fcl\u00fc kullan\u0131rken ve \u00e7\u0131k\u0131\u015f kodunun her zaman 0 olmad\u0131\u011f\u0131 ancak yine de ba\u015far\u0131l\u0131 oldu\u011fu durumlar i\u00e7in kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n- name: Bir komutu \u00e7al\u0131\u015ft\u0131r ve belirli bir \u00e7\u0131kt\u0131 varsa ba\u015far\u0131s\u0131z say\n ansible.builtin.shell: \/usr\/local\/bin\/my_custom_script.sh\n register: script_output\n failed_when: \"'ERROR' in script_output.stderr\"<\/code><\/pre>\nchanged_when<\/code><\/strong>: Bir g\u00f6revin ne zaman “de\u011fi\u015ftirildi” (changed) olarak raporlanaca\u011f\u0131n\u0131 tan\u0131mlar. Bu, idempotency’yi sa\u011flamak ve Ansible raporlamas\u0131n\u0131 do\u011fru hale getirmek i\u00e7in \u00e7ok \u00f6nemlidir. \u00d6rne\u011fin, bir komut her zaman \u00e7al\u0131\u015f\u0131r ancak yaln\u0131zca belirli bir ko\u015fulda sistemde ger\u00e7ek bir de\u011fi\u015fiklik yapar.<\/p>\n- name: Bir dosyay\u0131 g\u00fcncelle, ancak yaln\u0131zca i\u00e7erik de\u011fi\u015firse \"changed\" olarak i\u015faretle\n ansible.builtin.shell: \/usr\/local\/bin\/update_config.sh\n register: update_result\n changed_when: \"'UPDATED' in update_result.stdout\"\n # E\u011fer script her zaman 0 d\u00f6nd\u00fcr\u00fcyor ama bazen bir hata varsa, failed_when de ekleyebiliriz\n failed_when: \"'FAILED' in update_result.stderr\"<\/code><\/pre>\nAnsible Fact’leri ve Ko\u015fullar<\/h3>\n
setup<\/code> mod\u00fcl\u00fc varsay\u0131lan olarak t\u00fcm playbook’lar\u0131n ba\u015f\u0131nda fact’leri toplar.<\/p>\n
\n* ansible_os_family<\/code>: “Debian”, “RedHat”, “Windows”
\n* ansible_distribution<\/code>: “Ubuntu”, “CentOS”, “Fedora”
\n* ansible_distribution_major_version<\/code>: “20”, “8”
\n* ansible_processor_count<\/code>: CPU \u00e7ekirdek say\u0131s\u0131
\n* ansible_memtotal_mb<\/code>: Toplam bellek miktar\u0131 (MB)
\n* ansible_hostname<\/code>: Host ad\u0131
\n* ansible_default_ipv4.address<\/code>: Varsay\u0131lan IPv4 adresi<\/p>\n- name: Yaln\u0131zca 4'ten fazla CPU \u00e7ekirde\u011fi olan host'larda CPU yo\u011fun bir uygulama kur\n ansible.builtin.package:\n name: high_perf_app\n state: present\n when: ansible_processor_count > 4\n\n- name: Yaln\u0131zca belirli bir IP adresine sahip host'larda \u00f6zel bir yap\u0131land\u0131rma uygula\n ansible.builtin.template:\n src: special_config.j2\n dest: \/etc\/special_app.conf\n when: ansible_default_ipv4.address == \"192.168.1.100\"<\/code><\/pre>\nset_fact<\/code> mod\u00fcl\u00fcn\u00fc veya fact_caching<\/code> \u00f6zelli\u011fini kullanabilirsiniz.<\/p>\nJinja2 \u015eablon Motoru ve Ko\u015fullar<\/h3>\n
{% if %}<\/code>, {% elif %}<\/code>, {% else %}<\/code>, {% endif %}<\/code>). Bu, bir dosyan\u0131n i\u00e7eri\u011finin belirli ko\u015fullara g\u00f6re de\u011fi\u015fmesini sa\u011flamak i\u00e7in idealdir.<\/p>\n# templates\/my_app.conf.j2\nserver {\n listen {{ app_port }};\n server_name {{ inventory_hostname }};\n\n {% if environment == \"production\" %}\n access_log \/var\/log\/nginx\/{{ inventory_hostname }}_access.log main;\n error_log \/var\/log\/nginx\/{{ inventory_hostname }}_error.log warn;\n {% else %}\n access_log \/var\/log\/nginx\/{{ inventory_hostname }}_dev_access.log debug;\n error_log \/var\/log\/nginx\/{{ inventory_hostname }}_dev_error.log debug;\n {% endif %}\n\n location \/ {\n proxy_pass http:\/\/localhost:{{ backend_port }};\n }\n}<\/code><\/pre>\n- name: Uygulama yap\u0131land\u0131rma dosyas\u0131n\u0131 da\u011f\u0131t\n ansible.builtin.template:\n src: my_app.conf.j2\n dest: \/etc\/nginx\/conf.d\/my_app.conf\n vars:\n app_port: 80\n backend_port: 8080\n environment: \"production\" # Bu de\u011fi\u015fken Jinja2 \u015fablonu i\u00e7inde kullan\u0131lacak<\/code><\/pre>\nenvironment<\/code> de\u011fi\u015fkeninin de\u011ferine g\u00f6re access_log<\/code> ve error_log<\/code> ayarlar\u0131 farkl\u0131 olacakt\u0131r.<\/p>\nselect<\/code> ve reject<\/code> gibi filtreler sunar:<\/p>\n- name: Yaln\u0131zca belirli bir ko\u015fulu kar\u015f\u0131layan \u00f6\u011feleri i\u015fle\n ansible.builtin.debug:\n msg: \"\u00d6\u011fe: {{ item }}\"\n loop: \"{{ my_list | selectattr('status', 'equalto', 'active') | list }}\"\n vars:\n my_list:\n - { name: 'user1', status: 'active' }\n - { name: 'user2', status: 'inactive' }\n - { name: 'user3', status: 'active' }<\/code><\/pre>\nmy_list<\/code> i\u00e7indeki sadece status: active<\/code> olan \u00f6\u011feler d\u00f6ng\u00fcye al\u0131nacakt\u0131r.<\/p>\nEn \u0130yi Uygulamalar ve \u0130pu\u00e7lar\u0131<\/h3>\n
when<\/code> ifadelerini m\u00fcmk\u00fcn oldu\u011funca basitle\u015ftirin. Gerekirse birden fazla when<\/code> ifadesini ayr\u0131 ayr\u0131 sat\u0131rlarda kullan\u0131n veya karma\u015f\u0131k mant\u0131\u011f\u0131 de\u011fi\u015fkenlere atay\u0131n. Parantezleri do\u011fru kullanarak mant\u0131ksal operat\u00f6rlerin s\u0131ras\u0131n\u0131 netle\u015ftirin.
\n* De\u011fi\u015fken Kapsam\u0131:<\/strong> Ko\u015fullu ifadelerde kullan\u0131lan de\u011fi\u015fkenlerin do\u011fru kapsamda (host, grup, play, rol, g\u00f6rev) tan\u0131mland\u0131\u011f\u0131ndan emin olun.
\n* Fact’leri Ak\u0131ll\u0131ca Kullan\u0131n:<\/strong> Ansible fact’leri, sistem hakk\u0131nda g\u00fcvenilir bilgi sa\u011flar. Ko\u015fullar\u0131n\u0131z\u0131 olu\u015ftururken bu fact’lerden faydalan\u0131n. Ancak, \u00e7ok fazla fact toplamak performans\u0131 etkileyebilir, bu nedenle gereksiz fact toplamay\u0131 (gather_facts: false<\/code>) devre d\u0131\u015f\u0131 b\u0131rakmay\u0131 d\u00fc\u015f\u00fcnebilirsiniz.
\n* Test Edilebilirlik:<\/strong> Ko\u015fullu mant\u0131\u011f\u0131n\u0131z\u0131 k\u00fc\u00e7\u00fck, izole testlerle do\u011frulay\u0131n. debug<\/code> mod\u00fcl\u00fc, de\u011fi\u015fken de\u011ferlerini ve ko\u015fullu ifadelerin sonucunu kontrol etmek i\u00e7in \u00e7ok faydal\u0131d\u0131r.<\/p>\n- name: Ko\u015fulu test et\n ansible.builtin.debug:\n msg: \"Ko\u015ful do\u011fru mu? {{ ansible_os_family == 'Debian' and environment == 'production' }}\"<\/code><\/pre>\n
\n* Idempotency’yi Destekleme:<\/strong> changed_when<\/code> ve failed_when<\/code> gibi ifadelerle Ansible’\u0131n raporlamas\u0131n\u0131 do\u011fru hale getirerek otomasyonunuzun ger\u00e7ekten idempotent olmas\u0131n\u0131 sa\u011flay\u0131n.
\n* register<\/code> Kullan\u0131m\u0131:<\/strong> Bir \u00f6nceki g\u00f6revin \u00e7\u0131kt\u0131s\u0131n\u0131 register<\/code> ile bir de\u011fi\u015fkene kaydederek, bu \u00e7\u0131kt\u0131y\u0131 sonraki g\u00f6revlerdeki when<\/code> ifadelerinde kullanabilirsiniz.<\/p>\n- name: Bir komut \u00e7al\u0131\u015ft\u0131r\n ansible.builtin.shell: ls \/tmp\/my_file.txt\n register: file_check_result\n ignore_errors: true # Dosya yoksa hata vermesin\n\n - name: Dosya varsa bir i\u015flem yap\n ansible.builtin.debug:\n msg: \"Dosya var!\"\n when: file_check_result.rc == 0 # return code 0 ise dosya var demektir<\/code><\/pre>\nS\u0131k\u00e7a Yap\u0131lan Hatalar<\/h3>\n
is defined<\/code> kontrol\u00fc yapmadan onu bir ko\u015fulda kullanmaya \u00e7al\u0131\u015f\u0131rsan\u0131z, Ansible bir hata verir. Daima de\u011fi\u015fkenlerin varl\u0131\u011f\u0131n\u0131 kontrol edin (my_var is defined<\/code>).
\n* T\u00fcr Uyumsuzluklar\u0131:<\/strong> Kar\u015f\u0131la\u015ft\u0131rma yaparken de\u011fi\u015fkenlerin t\u00fcrlerini (string, integer, boolean) g\u00f6z \u00f6n\u00fcnde bulundurun. \u00d6rne\u011fin, ansible_processor_count<\/code> bir say\u0131 iken, environment<\/code> bir dize olabilir.
\n* Karma\u015f\u0131k Mant\u0131k Hatalar\u0131:<\/strong> \u00d6zellikle and<\/code> ve or<\/code> operat\u00f6rlerini bir arada kullan\u0131rken parantezlerin do\u011fru yerle\u015ftirilmesi \u00e7ok \u00f6nemlidir. Yanl\u0131\u015f parantez kullan\u0131m\u0131, beklenmedik sonu\u00e7lara yol a\u00e7abilir.
\n* when<\/code> ve failed_when<\/code> Kar\u0131\u015f\u0131kl\u0131\u011f\u0131:<\/strong> when<\/code> bir g\u00f6revin \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmayaca\u011f\u0131n\u0131 kontrol ederken, failed_when<\/code> \u00e7al\u0131\u015fan bir g\u00f6revin ba\u015far\u0131l\u0131 m\u0131 yoksa ba\u015far\u0131s\u0131z m\u0131 say\u0131laca\u011f\u0131n\u0131 kontrol eder. Ama\u00e7lar\u0131n\u0131 kar\u0131\u015ft\u0131rmay\u0131n.
\n* Liste Elemanlar\u0131n\u0131 Yanl\u0131\u015f Kontrol Etme:<\/strong> Bir listenin belirli bir \u00f6\u011feyi i\u00e7erip i\u00e7ermedi\u011fini kontrol etmek i\u00e7in do\u011frudan when: my_list == 'item'<\/code> yerine when: 'item' in my_list<\/code> kullan\u0131n.<\/p>\nSonu\u00e7<\/h3>\n
when<\/code> anahtar kelimesinden failed_when<\/code>, changed_when<\/code> gibi geli\u015fmi\u015f se\u00e7eneklere ve Jinja2 \u015fablonlar\u0131 i\u00e7indeki ko\u015fullara kadar geni\u015f bir yelpazede kullan\u0131m imkan\u0131 sunarlar. Ansible fact’lerini etkin bir \u015fekilde kullanarak sistemleriniz hakk\u0131nda bilgi toplayabilir ve bu bilgiyi otomasyon kararlar\u0131n\u0131zda kullanabilirsiniz.<\/p>\n
\n<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Ansible Playbook’larda Ko\u015fullu \u0130fadeler Nas\u0131l Kullan\u0131l\u0131r?\nAnsible, otomasyon d\u00fcnyas\u0131nda basitli\u011fi, arac\u0131s\u0131z mimarisi ve g\u00fc\u00e7l\u00fc yetenekle","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-35473","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-genel","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\n