globeandmail / ansible-role-amazon-cloudwatch-agent Goto Github PK

I'm getting the feeling that manually populating the TOML is not a supportable strategy.

First reason:

https://github.com/globeandmail/ansible-role-amazon-cloudwatch-agent/blob/master/ExampleCfgs/group_files/awscwa_cfg/generic/amazon-cloudwatch-agent.toml.j2#L49-L50
has the fields

      timestamp_layout = "{{logfile.timestamp_layout}}"
      timestamp_regex = "{{logfile.timestamp_regex}}"

but the TOML does not have a published schema,
and there is no corresponding field for either in the JSON schema...
-- therefore these fields appear to be undocumented.

Do you have any proposals as to how someone using this ansible-role should populate the above two fields?

It appears to me that keeping to using the JSON schema and letting the start-amazon-cloudwatch-agent script perform the JSON->TOML conversion is the only supportable method of using it.

Thoughts?

What tweaks did you find you needed to make between the JSON and the generated TOML?
Maybe you can share/document your tweaks as comments here or in the TOML?

Hi,

As per title, is it working with Ubutnu 18?

This request extends to all of globeandmail's ansible-role-* repos that lack a documented LICENSE.

• ansible-role-apt-cron
• ansible-role-nginx
• ansible-role-rpcbind
• ansible-role-nis
• ansible-role-postfix
• ansible-role-ntp
• ansible-role-nrpe
• ansible-role-sysstat
• ansible-role-motd
• ansible-role-newrelic-java-agent

thanks!