Public bug reported: The "Instance Metadata" documentation [1] describes nicely, how to use Jinja in cloud-config templates as well as shell scripts. It states that the first line must be
> ## template: jinja But only after reading the code, I found out that parsing only happens, when the MIME type is "text/jinja". Otherwise, the template is not parsed through Jinja. Running cloud-init 19.1 on Ubuntu 18.04 on AWS. [1] https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data ** Affects: cloud-init Importance: Undecided Status: New ** Attachment added: "cloud-init.yml" https://bugs.launchpad.net/bugs/1839814/+attachment/5282139/+files/cloud-init.yml -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1839814 Title: Docs: No info about Jinja templates require text/jinja mime type Status in cloud-init: New Bug description: The "Instance Metadata" documentation [1] describes nicely, how to use Jinja in cloud-config templates as well as shell scripts. It states that the first line must be > ## template: jinja But only after reading the code, I found out that parsing only happens, when the MIME type is "text/jinja". Otherwise, the template is not parsed through Jinja. Running cloud-init 19.1 on Ubuntu 18.04 on AWS. [1] https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1839814/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
