johndistasio / cauldron Goto Github PK

The current implementation of data.Json.GetData() uses ioutil.ReadAll(io.Reader) on the underlying io.Reader. As GetData() is intended to read from some kind of stream, this could cause a problem if accidentally or maliciously provided with a huge or never-ending stream.

Add some kind of limit here.

The JsonFile provider should be refactored into a general-purpose provider that accepts any io.Reader and parses whatever is read as JSON.

This could serve as the basis for other providers that consume JSON from the network instead of the local filesystem.

Follow up to #7

Expose HTTP header customization to the CLI; currently custom headers are supported but never set.

Title says it all - allow for reading generic JSON-formatted template data from any HTTP endpoint that would serve it.

Header customization should be a consideration here as at least some more-specific HTTP-based providers (e.g. GCP metadata store) require particular headers in order to function.

Add them.

https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-instancemetadataservice-overview

Add the ability to read template data from Azure metadata.

Add the ability to read template data from GCP instance and project metadata.

Add the ability to read template data from the AWS instance metadata service.

Script some functional tests that render templates to file and diffs the result with known good output.

Add the necessary bits and bobs to generate a generic Debian package.