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

core: move targets transform after flatten #2555

Merged
merged 1 commit into from
Jun 29, 2015
Merged

Conversation

phinze
Copy link
Contributor

@phinze phinze commented Jun 29, 2015

Allows target dependencies to be properly calculated across module
boundaries, fixing scenarios where a target depends on something inside
a module, but the contents of the module are not included in the
targeted resources.

fixes #1858

Allows target dependencies to be properly calculated across module
boundaries, fixing scenarios where a target depends on something inside
a module, but the contents of the module are not included in the
targeted resources.

fixes #1858
@phinze phinze added the core label Jun 29, 2015
@phinze
Copy link
Contributor Author

phinze commented Jun 29, 2015

ping @mitchellh for review

@phinze phinze added the bug label Jun 29, 2015
@mitchellh
Copy link
Contributor

LGTM

phinze added a commit that referenced this pull request Jun 29, 2015
core: move targets transform after flatten
@phinze phinze merged commit 6bbf61a into master Jun 29, 2015
@phinze phinze deleted the b-target-after-flatten branch June 29, 2015 18:35
@ghost
Copy link

ghost commented May 1, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

aws_instance security_groups getting only default when using -target= that points to a module security group
2 participants