Skip to content

Errors during init provide insufficient guidance when missing required fields #108

Closed
@jupierce

Description

Versions

Tectonic version (release or commit hash):

78e6f76292331a7fadc57ce3f362e558890fde84

Terraform version (terraform version):

Terraform v0.11.7

Platform (aws|azure|openstack|metal|vmware):

aws

What happened?

As a new user to tectonic init, tried populating aws config example. Clearly missing some fields in the file, but error output from is not always indicative of missing field:

15:47 $ tectonic init --config=examples/tectonic.aws.yaml
ERRO[0000] Found 1 error in the cluster definition:     
ERRO[0000] error 1: open : no such file or directory    
FATA[0000] found 1 cluster definition error   

What you expected to happen?

Error should identify which field is missing.

How to reproduce it (as minimally and precisely as possible)?

aws config file without required file fields.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    kind/documentationCategorizes issue or PR as related to documentation.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions