microsoft
Release to Environment - 0 Environments
My Release to Environment it does not seem to be pushing apps to the environment specified. What am I missing?
settings.json contains:
"environments": [
"QA",
"DEVTEST"
]
Log output shows no environments.
Trying to get environments from GitHub API main main EnvironmentsJson={"matrix":{"include":[]},"fail-fast":false} EnvironmentCount=0
GitHub Environments defined
Secrets defined in Repo
Im not sure if it makes a diffrence but I always configure my enviroments this way
And I never mention them in any settings file.
I have setup my Environments and Secrets per your suggestions and l have removed the environments from the settings.json. Still the same results. What am I missing?
Logs: logs_46.zip
I have a different error today related to the deployment from the CICD action. Does it shed any additional light? Ignore the DEV error it should updated at the moment. logs_66.zip
Looks like your refreshtoken expired or like
I have create the token per the PowerShell in this article: https://freddysblog.com/2022/05/06/deployment-strategies-and-al-go-for-github/
$AuthContext = New-BcAuthContext -includeDeviceLogin
Get-ALGoAuthContext -bcAuthContext $AuthContext | Set-Clipboard
I get a token that looks like this:
{"TenantID":"<tenantID>","Scopes":"https://api.businesscentral.dynamics.com/","RefreshToken":"0.AUgAgIe9q6...oZM"}
Which looks a little different than the token in your article. Your example does not start with {"TenantID":...
Does this look correct?
Yes, that is correct - the order of properties in the compressed json is random - in my sample, the tenantId and scopes is later (i.e. not visible)
The refreshtoken is only valid for 90 days though - it has to be renewed.
I have refreshed the token and now it does not error out but it doesn't deploy to any environments either.
Logs: logs_73.zip
Per @jonaswre I have set up my environments
and they match my environments.
What else do I need to do?
Looks correct - the pipeline just doesn't find them, cannot see why from here. You can add me to the repo, then I can see if I can see why
@freddydk I am just back from annual leave. Let me get organised and I will add you to the repo.
Did you manage to make this work - or are you still having issues with this?
I still have this problem and need assistance. Could we arrange some one on one time to work through this?
Did you upgrade to the latest version of AL-Go for GitHub and try on that one? If you have, and that fails, we can schedule a Teams call tomorrow 11:00 (CET timezone) if you like, then we can have a look at what's wrong. Please send and invite to freddyk at microsoft dot com, thanks