Closed algattik closed 2 years ago
Check that the user-provided prefix when running the Deploy action adheres to Azure naming conventions (and restrictions).
Run with valid prefix: https://github.com/agera-edc/MinimumViableDataspace/actions/runs/2825298663 Sample failed run with invalid prefix: https://github.com/agera-edc/MinimumViableDataspace/actions/runs/2825083999
https://github.com/agera-edc/MinimumViableDataspace/issues/152
no-changelog
What this PR changes/adds
Check that the user-provided prefix when running the Deploy action adheres to Azure naming conventions (and restrictions).
Why it does that
Further notes
Run with valid prefix: https://github.com/agera-edc/MinimumViableDataspace/actions/runs/2825298663 Sample failed run with invalid prefix: https://github.com/agera-edc/MinimumViableDataspace/actions/runs/2825083999
Linked Issue(s)
https://github.com/agera-edc/MinimumViableDataspace/issues/152
Checklist
no-changelog
)