Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relaxing restriction on empty datasources #316

Merged
merged 1 commit into from
May 4, 2018

Conversation

hairyhenderson
Copy link
Owner

Back when #200 was fixed (in #201), the assumption was made that if the data from the datasource was empty (i.e. an empty []byte), then this was an error condition and gomplate should effectively stop processing the datasource.

It turns out that this was actually a regression, and there are valid scenarios for having empty datasources - maybe a file is empty, and should be able to be parsed (like in #311).

I've re-thought this approach, and instead of being so heavy-handed, I'll allow empty datasources. In the specific Vault case (from #200), I'll simply return an error like I should've in the first place!

Signed-off-by: Dave Henderson dhenderson@gmail.com

@hairyhenderson hairyhenderson self-assigned this May 4, 2018
Signed-off-by: Dave Henderson <dhenderson@gmail.com>
@hairyhenderson hairyhenderson merged commit 195a6dc into master May 4, 2018
@hairyhenderson hairyhenderson deleted the relax-empty-datasource-error branch May 4, 2018 02:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant