-
Notifications
You must be signed in to change notification settings - Fork 1.1k
feat(discovery): add provider-neutral server discovery core #6143
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
base: feature/aws-iam-database-auth
Are you sure you want to change the base?
Changes from all commits
b0d0a59
e08e04b
55b0187
cb11503
52480f2
b16a60d
a858173
b4e1d3f
5184f8c
641b2cc
b141481
ac98d1f
4468aa2
a703376
eb9b18a
54a2827
61be693
d48e1cf
c26aa59
b912e5e
7511532
9a12670
283d077
f4bab01
503608b
75d98ae
3fc182d
603df52
3122b43
76e13e6
99c37c7
e777c0c
fcab78e
d97cbaf
24a8083
c917d08
b37cacb
29f1894
da36290
99c012a
4aa7970
e612b18
25ced1e
a24a6aa
bbf7749
19ad0b8
0062fbe
749c471
472fd5d
6f20080
0f7a2a1
180c6ec
1e3150e
9aaf4a2
dd63291
a3b671b
ef6a3cd
a104b23
8481c4f
354ea17
7c91137
c1bdc63
392402f
20b8b92
a3a02b5
d81a316
147022d
65f6308
6ff3ce3
86176ad
d744b5b
106e0d6
9f746c5
796f11f
92a994d
b106d33
e7898db
a4cf7c1
0a5c6a2
862200b
3e769b8
e0e3aaa
0eb6b3d
cba756c
e999cae
1ed576b
7814c87
19142c8
e1af5f2
daa9b82
37860e4
97a7179
6aaf073
7ea0d07
4763b24
4fc1a74
0ab6754
92c7111
47bd45b
5a19320
75972f4
3d4f172
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -111,16 +111,6 @@ jobs: | |
| run: | | ||
| PROXYSQL40=1 make ${{ env.MAKE_TARGET }} | ||
|
|
||
| - name: Verify package installs on clean ${{ env.DISTRO }} | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P2: This PR removes the only package-install verification for the arm64 almalinux10-genai package, and the change is unrelated to the PR's stated scope (server discovery core). The reusable gh-actions-reusable/verify-package-install.yml workflow exists but is not referenced by any workflow, so no replacement coverage is added — the package built here will be uploaded to the release without ever being installed on a clean distro. Re-add the step or wire in the reusable workflow; if the removal is intentional, document why in the PR description. Prompt for AI agents |
||
| run: | | ||
| PKG=$(ls binaries/*.deb binaries/*.rpm 2>/dev/null | head -1) | ||
| if [[ -z "$PKG" ]]; then | ||
| echo "ERROR: no package file found in binaries/" >&2 | ||
| ls -la binaries/ | ||
| exit 1 | ||
| fi | ||
| test/infra/control/verify-package-install.bash "$PKG" | ||
|
|
||
| - name: Upload to release | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -111,16 +111,6 @@ jobs: | |
| run: | | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P2: This PR removes the only package-install verification step in CI, and the PR description does not mention it. Prompt for AI agents |
||
| make ${{ env.MAKE_TARGET }} | ||
|
|
||
| - name: Verify package installs on clean ${{ env.DISTRO }} | ||
| run: | | ||
| PKG=$(ls binaries/*.deb binaries/*.rpm 2>/dev/null | head -1) | ||
| if [[ -z "$PKG" ]]; then | ||
| echo "ERROR: no package file found in binaries/" >&2 | ||
| ls -la binaries/ | ||
| exit 1 | ||
| fi | ||
| test/infra/control/verify-package-install.bash "$PKG" | ||
|
|
||
| - name: Upload to release | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -111,16 +111,6 @@ jobs: | |
| run: | | ||
| make ${{ env.MAKE_TARGET }} | ||
|
|
||
| - name: Verify package installs on clean ${{ env.DISTRO }} | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P2: This PR removes the only package-install verification for the arm64 centos9 package, and the removal is unrelated to the discovery feature. The reusable Prompt for AI agents |
||
| run: | | ||
| PKG=$(ls binaries/*.deb binaries/*.rpm 2>/dev/null | head -1) | ||
| if [[ -z "$PKG" ]]; then | ||
| echo "ERROR: no package file found in binaries/" >&2 | ||
| ls -la binaries/ | ||
| exit 1 | ||
| fi | ||
| test/infra/control/verify-package-install.bash "$PKG" | ||
|
|
||
| - name: Upload to release | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -111,16 +111,6 @@ jobs: | |
| run: | | ||
| make ${{ env.MAKE_TARGET }} | ||
|
|
||
| - name: Verify package installs on clean ${{ env.DISTRO }} | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P2: This PR removes the package-install verification step for arm64-fedora43, and the replacement reusable workflow (gh-actions-reusable/verify-package-install.yml) is not referenced by any workflow in this repository. If the GH-Actions branch caller does not invoke it for this distro, a package that fails to install on a clean Fedora 43 image will still be uploaded to the release. Confirm the reusable is wired up for arm64-fedora43, or keep the inline step. Prompt for AI agents |
||
| run: | | ||
| PKG=$(ls binaries/*.deb binaries/*.rpm 2>/dev/null | head -1) | ||
| if [[ -z "$PKG" ]]; then | ||
| echo "ERROR: no package file found in binaries/" >&2 | ||
| ls -la binaries/ | ||
| exit 1 | ||
| fi | ||
| test/infra/control/verify-package-install.bash "$PKG" | ||
|
|
||
| - name: Upload to release | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -113,16 +113,6 @@ jobs: | |
| run: | | ||
| PROXYSQL40=1 make ${{ env.MAKE_TARGET }} | ||
|
|
||
| - name: Verify package installs on clean ${{ env.DISTRO }} | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P2: This PR removes the only package-install verification for the fedora44-genai build, and the change is unrelated to the PR's stated goal (provider-neutral server discovery core). The removed step was the sole consumer of Prompt for AI agents |
||
| run: | | ||
| PKG=$(ls binaries/*.deb binaries/*.rpm 2>/dev/null | head -1) | ||
| if [[ -z "$PKG" ]]; then | ||
| echo "ERROR: no package file found in binaries/" >&2 | ||
| ls -la binaries/ | ||
| exit 1 | ||
| fi | ||
| test/infra/control/verify-package-install.bash "$PKG" | ||
|
|
||
| - name: Upload to release | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: sysown/proxysql
Length of output: 50372
🏁 Script executed:
Repository: sysown/proxysql
Length of output: 4670
🌐 Web query:
GitHub Actions documentation default GITHUB_TOKEN permissions pull_request workflow permissions omitted contents write💡 Result:
In GitHub Actions, the GITHUB_TOKEN does not have write access to repository contents or pull requests by default [1][2]. Because of security updates implemented by GitHub, modern repositories (created after February 2, 2023) default to read-only permissions for the GITHUB_TOKEN [1]. If your workflow requires the ability to push code, modify files, or manage pull requests (e.g., creating a pull request, adding labels, or merging), you must explicitly elevate the permissions within your workflow YAML file [1][2]. You can do this at the workflow or job level using the permissions key [3][4][5]. For example, to grant write access to both repository contents and pull requests, you should configure your workflow as follows: permissions: contents: write pull-requests: write When you define the permissions key, any permission not explicitly listed is set to none [6]. Therefore, if your workflow also requires other default access (such as reading metadata), you should explicitly include those as well, or ensure the overall set of permissions meets your needs [6][2]. It is important to note that when a workflow is triggered by a pull request from a forked repository, the GITHUB_TOKEN is restricted to read-only access by default to prevent unauthorized write operations, regardless of the permissions configured in the workflow, unless specific enterprise or organization settings allow otherwise [3][7][6]. Additionally, if you need to trigger further workflow runs (such as on: push or on: pull_request) using changes made by your workflow, the GITHUB_TOKEN cannot be used for that purpose; you must use a personal access token or a GitHub App installation access token instead [8][1].
Citations:
Security Misconfiguration (CWE-732): Incorrect Permission Assignment for Critical Resource
Reachability: External
Restrict the workflow token permissions.
This workflow runs repository-controlled scripts for
pull_requestevents. Add job-levelpermissions: contents: readso the job cannot inherit broader repository or organization defaults.🧰 Tools
🪛 zizmor (1.29.0)
[warning] 9-53: overly broad permissions (excessive-permissions): default permissions used due to no permissions: block
(excessive-permissions)
🤖 Prompt for AI Agents
Source: Linters/SAST tools