Remove explicit/default lookup pointing at output
#298
Labels
Milestone
Comments
phobologic
added a commit
that referenced
this issue
Jan 29, 2017
This removes the old functionality where if a lookup was called, but no
lookup handler was given, it would default to using `output`. IE:
```
SomeVariable: ${vpc::PublicSubnets}
```
must now explicitly call to the output lookup handler:
```
SomeVariable: ${output vpc::PublicSubnets}
```
Fixes #298
phobologic
added a commit
that referenced
this issue
Jan 29, 2017
This removes the old functionality where if a lookup was called, but no
lookup handler was given, it would default to using `output`. IE:
```
SomeVariable: ${vpc::PublicSubnets}
```
must now explicitly call to the output lookup handler:
```
SomeVariable: ${output vpc::PublicSubnets}
```
Fixes #298
This was referenced Feb 4, 2017
Merged
|
Fixed in #310 |
phrohdoh
pushed a commit
to phrohdoh/stacker
that referenced
this issue
Dec 18, 2018
This removes the old functionality where if a lookup was called, but no
lookup handler was given, it would default to using `output`. IE:
```
SomeVariable: ${vpc::PublicSubnets}
```
must now explicitly call to the output lookup handler:
```
SomeVariable: ${output vpc::PublicSubnets}
```
Fixes cloudtools#298
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now if you don't specify the lookup you're using, it'll default to
output, as detailed here: http://stacker.readthedocs.io/en/latest/lookups.htmlAfter a chat in the Slack, folks seemed to agree that this shortcut wasn't necessary, and could lead to confusion and/or other issues. It also complicates the code a bit.
To do that, the plan is to remove this feature in 1.0.
The text was updated successfully, but these errors were encountered: