Upgrade GitHub App Azure-Sentinel

George Zerphey 136

We have been using the Azure-Sentinel GitHub App to synchronize our repository to Sentinel. Its been a while since its been installed and lately we have been getting the following error:

deploy-content Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: azure/login@v1, azure/powershell@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Is there a way to trigger an update of the GitHub App or reinstall it without losing the connection information we have in the system?

Thank you,

Marilee Turscak-MSFT 36,936 Reputation points Microsoft Employee

2024-05-20T21:31:00.8+00:00

@George Zerphey Thanks for your post! We are looking into this and will get back to you.
Marilee Turscak-MSFT 36,936 Reputation points Microsoft Employee

2024-05-21T01:44:02.8433333+00:00

Hi @George Zerphey ,

There isn't an out-of-the-box way through Microsoft to do the update automatically that I am aware of, but you can use other tools (Github Actions Updater, Dependabot, renovatebot) to run the updates automatically. I cannot personally attest to these but there is more information in these posts:

https://github.com/marketplace/actions/github-actions-version-updater

https://stackoverflow.com/questions/76056803/update-your-actions-to-run-on-node-16-instead-of-node-12-on-github

It might be best to reach out to Github support for more detailed instructions. https://support.github.com/
George Zerphey 136 Reputation points

2024-05-21T12:33:22.8733333+00:00

Is there a place I can get access to the latest official Sentinel-Deploy yml for the app? I think the problem is the current yml works with outdated versions.

I think if we can update the yml with the latest information it will fix the problem.

For example I'm fairly certain that checkout is on version 3 or 4
George Zerphey 136 Reputation points

2024-05-21T12:35:44.38+00:00

For example I'm pretty sure that checkout is on v3 at this point.
George Zerphey 136 Reputation points

2024-05-22T14:23:01.0466667+00:00

@Marilee Turscak-MSFT Just bumping this to see if you have a new version of powershell or login that utilizes the updated node settings. A recent sentinel we brought on also seems to have v1 on login and powershell. Checkout however is updated to v3.

Thank you,

1 answer

George Zerphey 136 Reputation points

2024-05-22T19:18:36.3833333+00:00
I have found an answer to this for everyone in the future. I had to get the latest ps1 file from Sentinel by connecting it to a new repo and made a few alterations to the yml file. @Marilee Turscak-MSFT As a side-note it would be really helpful to understand where these yml templates and ps1 files are stored so we can watch them for updates

YML Updates:

Checkout had to be changed to version 4.

name: Checkout uses: actions/checkout@v4

Login had to be changed to version 2. These had to be changed for each login retry.

steps: - name: Login to Azure (Attempt 1) continue-on-error: true id: login1 uses: azure/login@v2

Powershell needed to be changed to version 2

name: Deploy Content to Azure Sentinel uses: azure/powershell@v2
Please sign in to rate this answer.

1 person found this answer helpful.
Marilee Turscak-MSFT 36,936 Reputation points Microsoft Employee

2024-05-22T22:55:11.67+00:00

@George Zerphey Thanks for sharing your solution. I've reached out internally to check about the files. It looks like some of the documents may be in the process of getting updated.

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sentinel/ci-cd-custom-deploy.md
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Upgrade GitHub App Azure-Sentinel

1 answer

Your answer