-
Notifications
You must be signed in to change notification settings - Fork 437
'Publish' 'changed' child-resources #331
Copy link
Copy link
Closed
Labels
[cat] modulescategory: modulescategory: modules[cat] pipelinescategory: pipelinescategory: pipelines[cat] publishingcategory: publishingcategory: publishing[prio] highimportance of the issue: high priorityimportance of the issue: high priorityenhancementNew feature or requestNew feature or request
Milestone
Metadata
Metadata
Assignees
Labels
[cat] modulescategory: modulescategory: modules[cat] pipelinescategory: pipelinescategory: pipelines[cat] publishingcategory: publishingcategory: publishing[prio] highimportance of the issue: high priorityimportance of the issue: high priorityenhancementNew feature or requestNew feature or request
For modules that align with the child-resource structure (i.e. use child-templates #236) we want to make sure the child-templates (e.g.
container/deploy.bicep) are published the same way as their corresponding parent template is.However, for that to work we have to make sure only templates that actually changed are included in the publish - not the entire module tree (i.e. parent + all rescursive children).