fix expansion for the case of ENV var is not set #299
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a 🐞 bug fix.
bundle exec rspec
to verify this)Summary
As per docs, with Terraspace v2, any environment variable is also available in the expansion helper. IE: MY_VAR=foo can be use in the expansion(":MY_VAR") method.
This works as expected if MY_VAR is set to some value, but in case environment variable MY_VAR is not set it's returning as it is in non-expanded state like ":MY_VAR"
Now with this fix, it returns empty space if environment variable is not set. Unit test case is also updated.
Context
How to Test
Just run the unit test
rspec spec/terraspace/provider/expander/generic_spec.rb
Version Changes