3 Commits (1bb154de5abb64aaf1ed56ffff5f8fda4e7a520f)

Author	SHA1	Message	Date
Wilken Rivera	1bb154de5a	Add support for reading configs ... This is the first step in attempting to read a Packer configuration file via the packer init command. At the present moment it will try to read one or more configuration templates from a given directory or path. Once parsed it will error if parsing fails or exist successfully if it is able to parse the file. Looking at how the code is structured there will need to be changes made to the following places: - When no configuration file is found Packer will display an error. That error should be bubbled up a bit so that the caller command can determine if it should be displayed or not. For packer init no configuration is not an error. Maybe it should be? - After a configuration has been parsed there needs to be a single way to determine a list of plugins associated with the configuration. HCL and JSON configs have fields for this data but some is exported and some is unexported. Adapting the packerHandler interface may be an option here. More investigation needed.	6 years ago
Wilken Rivera	8069ae4f43	Add flagset to init command	6 years ago
Wilken Rivera	e8f7076416	Add simple init command	6 years ago