Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

'Publish' 'changed' child-resources #331

Closed
AlexanderSehr opened this issue Nov 1, 2021 · 1 comment · Fixed by #744
Closed

'Publish' 'changed' child-resources #331

AlexanderSehr opened this issue Nov 1, 2021 · 1 comment · Fixed by #744
Assignees
@AlexanderSehr @MariusStorhaug
Labels
[cat] modules category: modules [cat] pipelines category: pipelines [cat] publishing category: publishing enhancement New feature or request [prio] high importance of the issue: high priority
Milestone
v 0.4

Comments

@AlexanderSehr
Copy link
Contributor

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).
@AlexanderSehr AlexanderSehr added the enhancement New feature or request label Nov 1, 2021
@AlexanderSehr AlexanderSehr added this to the Public Preview milestone Nov 1, 2021
@rahalan rahalan added [prio] high importance of the issue: high priority [cat] modules category: modules [cat] pipelines category: pipelines labels Nov 4, 2021
@rahalan rahalan changed the title Pipline: 'Publish' 'changed' child-resources 'Publish' 'changed' child-resources Nov 4, 2021
@rahalan rahalan added [cat] publishing category: publishing and removed [prio] high importance of the issue: high priority labels Nov 4, 2021
@AlexanderSehr AlexanderSehr modified the milestones: v 0.3, v 0.4 Nov 29, 2021
@MariusStorhaug
Copy link
Contributor

MariusStorhaug commented Dec 2, 2021 •
edited
Loading

Change to arm/<resourceProvider>/<resourceType>/<childResource> should publish new version of itself (only).
What is there is a major/minor change. Should parents also be updated with new version?

@MariusStorhaug MariusStorhaug linked a pull request Dec 6, 2021 that will close this issue
Publishing and versioning of child-resources and parents #744
Merged
29 tasks
@rahalan rahalan added the [prio] high importance of the issue: high priority label Dec 6, 2021
@AlexanderSehr AlexanderSehr mentioned this issue Dec 6, 2021
Open
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@AlexanderSehr AlexanderSehr

@MariusStorhaug MariusStorhaug

Labels
[cat] modules category: modules [cat] pipelines category: pipelines [cat] publishing category: publishing enhancement New feature or request [prio] high importance of the issue: high priority
Projects
None yet
Milestone
v 0.4
Development

Successfully merging a pull request may close this issue.

Publishing and versioning of child-resources and parents Azure/ResourceModules
3 participants
@AlexanderSehr @MariusStorhaug @rahalan