KEDA cannot parse PEM certificate from Azure Container Apps secrets when using GitHub Runner scaler #1234
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: Automatically add new issue to backlog | |
| on: | |
| issues: | |
| types: | |
| - opened | |
| jobs: | |
| track_issue: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: Get project data | |
| env: | |
| GITHUB_TOKEN: ${{ secrets.GH_AUTOMATION_PAT }} | |
| ORGANIZATION: kedacore | |
| # This refers to our backlog project: https://github.com/orgs/kedacore/projects/2/views/1 | |
| PROJECT_NUMBER: 2 | |
| run: | | |
| gh api graphql -f query=' | |
| query($org: String!, $number: Int!) { | |
| organization(login: $org){ | |
| projectV2(number: $number) { | |
| id | |
| fields(first:20) { | |
| nodes { | |
| ... on ProjectV2Field { | |
| id | |
| name | |
| } | |
| } | |
| } | |
| } | |
| } | |
| }' -f org=$ORGANIZATION -F number=$PROJECT_NUMBER > project_data.json | |
| echo 'PROJECT_ID='$(jq '.data.organization.projectV2.id' project_data.json) >> $GITHUB_ENV | |
| - name: Add issue to project | |
| env: | |
| GITHUB_TOKEN: ${{ secrets.GH_AUTOMATION_PAT }} | |
| ISSUE_ID: ${{ github.event.issue.node_id }} | |
| run: | | |
| item_id="$( gh api graphql -f query=' | |
| mutation($project:ID!, $issue:ID!) { | |
| addProjectV2ItemById(input: {projectId: $project, contentId: $issue}) { | |
| item { | |
| id | |
| } | |
| } | |
| }' -f project=$PROJECT_ID -f issue=$ISSUE_ID --jq '.data.addProjectV2ItemById.item.id')" |