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 Dependency Support #131

Closed
alanp-msft opened this issue Aug 4, 2020 · 8 comments
Closed

Module Dependency Support #131

alanp-msft opened this issue Aug 4, 2020 · 8 comments

Comments

@alanp-msft
Copy link

Will module support dependency, such as Module1 depends on Module A, or an array of Modules, etc.?

@alex-frankel
Copy link
Collaborator

You will be able to chain modules together such that Module1 instantiates Module 2 which itself instantiates Module 3, etc.

@alex-frankel
Copy link
Collaborator

@alanp-msft - did this clarify? I will plan to close if I don't hear back

@alanp-msft
Copy link
Author

Hi, @alex-frankel and @satyavel , thanks for clarifying. I am also wondering any plans to make module as more of unit of work (deployment) to maintain their own "state" supporting independent life cycle, and have its own cadence, etc. per our discussion last week. Another aspect of module I am interested, how module can be consumed, shared, etc. Is there any defined roadmap for composition from both type composition and deployment composition perspective?

@alex-frankel
Copy link
Collaborator

The modules are going to be represented as a nested inline deployments in the ARM JSON, so you would be able to do some of the redeployment scenarios you showed us by simply retrying the specific deployment. Since we are turning them into the deployments, I think the foundation is there to do the rest.

@alanp-msft
Copy link
Author

That is great. I like to see how that could be surfaced and additional functionality, such as retry, composition, etc. provided around it, this will be very powerful.

@alex-frankel
Copy link
Collaborator

great! going to close this as it looks like we are in sync

@takekazuomi
Copy link
Contributor

It seems that dependsOn is automatically generated when referencing the outputs of the module from other modules. Therefore, I think there is a not need for an additional dependency definition mechanism.

@majastrz
Copy link
Collaborator

In some cases, we are not able to figure out dependencies between modules. To deal with that, users need to be able to set the dependencies however they need. This will be accomplished via explicit dependsOn just like with resources.

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

4 participants