Deploy App using PR build - Publish To Environement using PR

[ismailhafid1]

For deployment in the environment, we tested different approaches.
The first approach is to deploy using only the app.
The second approach is to deploy using the app and dependencies from the app source.
And the third approach is to use deployments with the dependencies that exist only in GitHub, but not in the Appsource, because it's an internal product.
All the previous approches are working fine.
but the last approach that we tried to test, but we didn't get a successful workflow run, is running the published environment using the PR build. It always returns 403 forbidden errors.
Artifact generated from PR build:

Publish To Environnement PR :

All the the other approches uses the same Entra App and the same environnement and it s working fine , maybe i am missing an extra parameter that i didn't se ?

[freddydk]

This might be a bug - we will investigate that.
@spetersenms - does the job have sufficient permissions to query prior successful builds in a private repository?`
(I think actions: read and pull request: read might be needed)

[ismailhafid1]

any update ?

[freddydk]

In your logs, I can see that you are running with a preview version, which is 3+ weeks old - could you update to v7.1 - just to see whether the problem has been fixed since then.
If v7.1 doesn't fix this, then please try the following (just to see whether this fixes the issue):

Modify .github/workflows/PublishToEnvironment.yaml and change:

permissions:
  actions: read
  contents: read
  id-token: write

to:

permissions:
  actions: read
  contents: read
  pull-requests: read
  id-token: write

and try again.

Let me know whether v7.1 fixed the issue or the permissions fix (which according to the documentation shouldn't be necessary)

[ismailhafid1]

ok , i found the error , i was selecting main branch instead of the PR branch to deploy the PR version , i was following this image from directions:

it would helpful if the error message was more clear if the branch used to deploy the PR version is not the right one

[freddydk]

That should not be necessary - you should be able to run the workflow from main, if your main branch is updated.
right @spetersenms ?

[ismailhafid1]

hmm , with the main branch even if i added the permissions and i updated the ALGO to the latest version from your previous reply , it returned the same error ,

[spetersenms]

Hi @ismailhafid1, apologies for the late response. I have taken a look and found that the error is caused by a permissions issue in private repos. I am working on a fix that will be available shortly.

[spetersenms]

A new preview version was just deployed with the fix. Also to confirm on the above discussion with Freddy, the main branch should be used when running the action.