Track Github action and its warnings

[Ponnia-M]

As a VRO Engineer, we faced multiple warnings when it comes to deploying code through our pipelines. We investigated these warnings and fixed most of them so that we can deploy code more seamlessly. However, some workflows are still affected by this warnings:

• The following actions uses node12 which is deprecated and will be forced to run on node16: indiesdev/curl@v1.1.
• The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

I contacted the engineer in charge of maintaining this Github action, but got no response. This ticket is to maintain visibility and keep track of this issue and hopefully update it in the future.

Github Actions workflows affected by warnings above:

1. Continuous Integration (CI) workflow => 26 warnings across various jobs
2. CI: API Gateway integration test => 10 warnings (mostly deprecated 'set-output' command)
3. CI: BIE Kafka End-2-End Test => 2 warnings
4. CI: EE - EP Merge - Integration Test => 4 warnings
5. CI: SVC BGS API integration test => 9 warnings
6. CI: SVC BIP API integration test => 2 warnings
7. Secrel => 6 warnings

Team agreed that we retired indiesdev/curl@v1.1 action and replace it with another since it's no longer managed consistently.

[Ponnia-M]

tspascoal/get-user-teams-membership@v3.0.0 is up to date and changes have been merged to develop branch

[Ponnia-M]

Created ticket to change private repo (curl-action) to public

[Ponnia-M]

Still waiting on approval from VA COR then update this ticket

[Ponnia-M]

Created a new action in public VA repo. Below are links to affected workflows and no more node.js 16 errors come up anymore since these actions now run on Node.js 20:

• BIE-Kakfa
• BIP-API
• BGS-API
• EE-EP merge
• API gateway
• CI
• Secrel => For clarity, all indiesdev/curl@v1.1 action warnings in our Secrel workflow have been resolved. However, the current node.js 16 warnings seen here are from another action (see picture below). Based on this conversation reverting back to v5 brought back these errors.

Here is the updated PR.