Azure / Azure/ResourceModules

[Feature Request]: Test the publishing logic

Open
#2,611 1 comment 0 reactions 3 assignees Claimed by @MariusStorhaug View on GitHub
enhancement
Dominant language
PowerShell
Stars
737
Forks
436
Avg merge
10d 7h
Merged PRs (30d)
1

Description

### Description

| Test Feature\Env | | GitHub | Azure DevOps |
| - | - | - | - |
| Non-existing target | | | |
| | ACR | | |
| | ACR Pre-release | | |
| | Template Specs | | |
| | Template Specs Pre-release | | |
| Misc |
| | Publish only changed modules |
| | Publish parent & child modules |
| | Test if the publish step actually fails (red) upon error |
| Latest |
| | Publish if flag enabled |
| | Publish not if flag disabled |
| | Publish not if flag enabled + pre-release |
| | Publish not if flag disabled + pre-release |
| Major/minor |
| | Publish not if pre-release |
| | Publish if not pre-release |

| Legend | |
| - | - |
| Success | ✅ |
| Failed | :x: |

Found issues:
- Pre-release publishing of a non-existent module publishes also minor, major & latest (latest even if the corresponding flag is disabled)

Other actions:
- Implement logic to determine if anything is published before the actual publishing steps to also visually show that a publish took place or not

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.