Expanded packages/backend-common with MySQL Tests
Updated packages/backend-tasks column types to conform to MySQL
Updated packages/backend-tasks database tests with MySQL
Updated packages/backend-tasks datetime column to work with MySQL
Updated packages/create-app with a production MySQL App Config template
Updated packages/e2e-test to allow for e2e testing with MySQL
Updated plugins/app-backend some text columns to string
Updated plugins/app-backend interval to work with MySQL
Updated plugins/bazaar-backend to run db tests against MySQL
Updated plugins/catalog-backend-module-incremental-ingestion to run
db tests against MySQL
Updated plugins/catalog-backend text columns to longtext to work
with MySQL like issue suggested
Updated plugins/code-coverage-backend text column to string
Updated plugins/linguist-backend text column to string
Updated plugins/tech-insights-backend text columns to string
Updated plugins/tech-insights-backend db tests to include MySQL
Added New E2E tests to run on pull requests to test against MySQL
Co-authored-by: Alex Rocha <alexr1@vmware.com>
Co-authored-by: David Alvarado <dalvarado@vmware.com>
Co-authored-by: Shwetha Gururaj <gururajsh@vmware.com>
Co-authored-by: Al <aberezovsky@vmware.com>
Co-authored-by: Gerg <gcobb@vmware.com>
Signed-off-by: Pete Levine A <lpete@vmware.com>
Signed-off-by: lpete@vmware.com <lpete@vmware.com>
Fixes SNYK-JS-FASTXMLPARSER-5668858
by upgrading aws-sdk dependencies to
their latest version.
The upgrade of `fast-xml-parser` to
version 4.2.4 (or higher) was included
in release v3.347.1 of the aws-sdk.
Latest release is v3.350.0, however,
not for all packages.
The previous version's requirement would have
allowed to use a newer version of the aws-sdk
to fix it locally to a backstage project setup.
This change will enforce a version including the fix.
Closes: #18164
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
Support commit hashes additionally to branch names at the `GithubUrlReader`'s `readTree` and `search`.
This is achieved by using the "combined commit status" API instead of the branch API
which works with commit hashes and branch names.
When used with branch names, it will return the result for the HEAD of the branch
which is what the branch API was used for before.
We are not really interested in commit statuses, though, and can ignore them.
The "combined commit status" API support branch names with slashes as well, like `branch/name`.
Additionally, this will reduce the number of API calls from 2 to 1 for retrieving the "repo details"
for all cases besides when the default branch has to be resolved and used
(e.g., repo URL without any branch or commit hash).
Relates-to: PR #16721
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
github-actions[bot]