Move admin center / publish to env authentication to action rather than inline powershell #2116
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
❔What, Why & How
Problem
Right now, the "Publish to Environment" and "Create Online Dev. Environment" workflows will fail when no Authcontext is provided. AL-Go is supposed to use the DeviceCode flow when we're lacking an Authcontext but in order to run DownloadAndImportBcContainerHelper we need to import the DebugHelper.psm1. Right now we don't, so we see failures around "OutputDebug" not being recognized.
Proposed Solution
Both workflow use an inline powershell script. We could move this to its own AL-Go action where the script is invoked with Invoke-AlGoAction.ps1. That way we ensure that DebugLogHelper is imported.
Related to issue: #2113
✅ Checklist