Skip to content

Testing PoC: Modules should be more self-contained for testing #329

@AlexanderSehr

Description

@AlexanderSehr

Initial description

Modues are currently dependent on pre-deployed dependencies to work (e.g. VNETs, MSIs, etc.).

It would be better if we'd have a universal logic that allows modules to deploy their own dependencies instead. Ideally even in their own resource group (for Rg-Level resources) so that we can just remove the resource group instead of individual resources from it.

Update # 1:

It was decided to have a single dependency file per module and deploy it before the parameter file deployments - and remove the dependency resources afterwards again.

Current pipeline

The current pipeline looks like

image

There are different variants we could implement, as documented in the following:

Variant 1

There is one simply approach (which we discarded):
image

The following two pipeline variants will be implemented as part of a PoC:

Variant 2

image

Variant 3

image

Other options:

Update # 2:

Variant 4

image

Variant 5

image

Analysis Services Example
image

It was further decided to use plain resources (not our own modules) in the dependency file(s).

Note: Regardless of the implemented approach we should add features such as the Parameter-Matrix & Stage-template for Azure DevOps.

Metadata

Metadata

Labels

[cat] testingcategory: testing[prio] highimportance of the issue: high priorityenhancementNew feature or request

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions