yahoo-eng-team team mailing list archive

[StephenKing <1839814@xxxxxxxxxxxxxxxxxx>]

Oh..

> If you're choosing the specify a mime type, then you do have to choose
the correct mime type.

By that you obviously mean the mime type is optional. D'oh.. I thought
it's required, but actually it's optional also in Terraform - and the
one who has put the wrong value there was obviously me.

Sorry for that mistake, thanks for helping me!

Steffen

** Changed in: cloud-init
       Status: Incomplete => Invalid

-- 
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:
  Invalid

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