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

Module fails if/when dependencies do not exist yet. #50

Open
alex-goncharov opened this issue Nov 14, 2019 · 1 comment
Open

Module fails if/when dependencies do not exist yet. #50

alex-goncharov opened this issue Nov 14, 2019 · 1 comment

Comments

@alex-goncharov
Copy link
Contributor

Due to AzureRM provider bug or feature, the name of the resource is known before it is actually created. Therefore terraform cannot build the dependency tree appropriately and it does not wait for dependency to be created.

For example, a key vault data source fails if key vault does not exist yet, even though it is being created by the same plan.

In my opinion, the module should accept and use resource ID instead, which is know after resource creation and therefore allows terraform to build a working dependency tree

@straubt1
Copy link
Contributor

Totally agree with this as it would also allow the resources in the module to be created in a different RG than the networking pieces.

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

No branches or pull requests

2 participants