Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto Generated Indexes v2 #1472

Open
wants to merge 10 commits into
base: develop
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 9 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,14 @@ on:
workflow_dispatch:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mbellifa after discussing with the team I think it would be better to run this in a separate GHA that runs on PRs to develop vs adding it to the release workflow. This will ensure develop stays in sync with main and let us test it more thoroughly prior to each release.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@arielkr256 Would a workflow that triggered on a push to develop work? I'm thinking of using a filter that only runs when .yml files are changed so it doesn't loop. My concern with PRs is I'm reading that they can have different behavior/permission issues when a PR is opened from a fork, and I can envision increased merge conflicts if the indexes are built within the PRs themselves.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes I think that sounds great!


permissions:
contents: read
contents: write

jobs:
release:
runs-on: ubuntu-latest
permissions:
id-token: write
contents: read
contents: write
env:
GITHUB_TOKEN: ${{ secrets.PANTHER_BOT_AUTOMATION_TOKEN }}
steps:
Expand All @@ -32,6 +32,17 @@ jobs:
uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b #v5.3.0
with:
python-version: "3.11"
- name: Install dependencies
run: pip3 install -r ./.scripts/requirements.txt
- name: Generate indexes
run: python3 ./.scripts/generate_indexes.py
- name: Commit Indexes
run: |
git config user.email "[email protected]"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@c0nfleis @canagno123 is this the right email to use for the bot?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's use the panther-bot-automation, like so:

git config --global user.email "[email protected]"
git config --global user.name "panther-bot-automation"

git config user.name "Panther Bot"
git add ./indexes
git commit -m "Update indexes"
git push --no-sign
- name: Create new panther-analysis release
run: |
export AWS_REGION=${{ secrets.AWS_REGION }}
Expand Down
Loading
Loading