Conversation

Notices

1. Embed this notice
   scetron (scetron@techhub.social)'s status on Tuesday, 26-Mar-2024 20:13:16 JST scetron

   in reply to

   • Marcos Dione
   • Dennis Hoppe

   @mdione @dhoppe I always find it easier to debug jinja by removing all of the template and adding it back piece by piece…

   That or copying the variables that go into it into a fixture and using that with a playbook with just the jinja and vars.

   • Embed this notice
     Marcos Dione (mdione@en.osm.town)'s status on Tuesday, 26-Mar-2024 20:13:17 JST Marcos Dione

     in reply to

     • Dennis Hoppe

     @dhoppe thanks. That means that now I "only" have to extract the variable information from #ansible. As that aspect of ansible is quite complex to reproduce, I will have to rely on Ansible itself. Maybe one could use it as a module and ask it to generate that?

   • Embed this notice
     Dennis Hoppe (dhoppe@chaos.social)'s status on Tuesday, 26-Mar-2024 20:13:29 JST Dennis Hoppe

     in reply to

     • Marcos Dione

     @mdione This tool was recommended by someone some time ago.
     https://github.com/kpfleming/jinjanator

   • Embed this notice
     Marcos Dione (mdione@en.osm.town)'s status on Tuesday, 26-Mar-2024 20:13:31 JST Marcos Dione

     I keep looking for ways to debug #jinja templates under #ansible. Seems like the answer is that you can't debut Jinja templates at all.

     PS: boosts and tips welcome.

     #python