Merge branch 'master' into docs/writing-custom-field-extension_add-imports

feat: update branch from backstage/backstage.

docs/backend-system/building-plugins-and-modules/02-testing.md

@@ -224,10 +224,7 @@ your test database.
 ```ts
 const { knex, subject } = await createSubject(databaseId);
 const { server } = await startTestBackend({
-  features: [
-    myPlugin(),
-    mockServices.database.mock({ getClient: async () => knex }),
-  ],
+  features: [myPlugin(), mockServices.database.factory({ knex })],
 });
 ```
 

docs/features/kubernetes/configuration.md

@@ -17,6 +17,9 @@ The following is a full example entry in `app-config.yaml`:
 
 ```yaml
 kubernetes:
+  frontend:
+    podDelete:
+      enabled: true
   serviceLocatorMethod:
     type: 'multiTenant'
   clusterLocatorMethods:
@@ -48,6 +51,55 @@ kubernetes:
       exposeDashboard: true
 ```
 
+### `frontend` (optional)
+
+This is an array used to configure some frontend features.
+
+Valid values are:
+
+- `podDelete`
+
+#### `podDelete` (optional)
+
+This configures the behavior of the delete pod button in the container panel.
+
+Valid configurations are:
+
+- `enabled`
+
+##### `enabled`
+
+This configuration controls the visibility of this feature.
+
+Valid values are:
+
+- `true`
+- `false`
+
+The default value is `false`.
+
+#### Internationalization
+
+To customize or translate the **Delete Pod** text, use the following approach:
+
+```js
+import { createTranslationMessages } from '@backstage/core-plugin-api/alpha';
+import { kubernetesReactTranslationRef } from '@backstage/plugin-kubernetes-react/alpha';
+
+const app = createApp({
+  __experimentalTranslations: {
+    resources: [
+      createTranslationMessages({
+        ref: kubernetesReactTranslationRef,
+        messages: {
+          "podDrawer.buttons.delete": 'Restart Pod'
+        }
+      })
+    ]
+  },
+  ...
+```
+
 ### `serviceLocatorMethod`
 
 This configures how to determine which clusters a component is running in.

docs/features/software-templates/index.md

@@ -25,7 +25,9 @@ locations like GitHub or GitLab.
 If you're running Backstage with Node 20 or later, you'll need to pass the flag `--no-node-snapshot` to Node in order to
 use the templates feature.
 One way to do this is to specify the `NODE_OPTIONS` environment variable before starting Backstage:
-`export NODE_OPTIONS=--no-node-snapshot`
+`export NODE_OPTIONS="${NODE_OPTIONS:-} --no-node-snapshot"`
+
+> It's important to append to the existing `NODE_OPTIONS` value, if it's already set, rather than overwriting it, since some NodeJS Debugging tools may rely on this environment variable to work properly.
 
 :::
 

docs/getting-started/index.md

@@ -35,11 +35,12 @@ This guide assumes a basic understanding of working on a Linux based operating s
   - Using `nvm` (recommended)
     - [Installing nvm](https://github.com/nvm-sh/nvm#install--update-script)
     - [Install and change Node version with nvm](https://nodejs.org/en/download/package-manager/#nvm)
+    - Node 20 is a good starting point, this can be installed using `nvm install lts/iron`
   - [Binary Download](https://nodejs.org/en/download/)
   - [Package manager](https://nodejs.org/en/download/package-manager/)
   - [Using NodeSource packages](https://github.com/nodesource/distributions/blob/master/README.md)
-- `yarn` [Installation](https://classic.yarnpkg.com/en/docs/install)
-  - You will need to use Yarn classic to create a new project, but it can then be [migrated to Yarn 3](../tutorials/yarn-migration.md)
+- `yarn` [Installation](https://yarnpkg.com/getting-started/install)
+  - Backstage currently uses Yarn 4.4.1, once you've ran `corepack enable` you'll want to then run `yarn set version 4.4.1`
 - `docker` [installation](https://docs.docker.com/engine/install/)
 - `git` [installation](https://github.com/git-guides/install-git)
 - If the system is not directly accessible over your network the following ports
@@ -142,16 +143,18 @@ Choose the correct next steps for your user role, if you're likely to be deployi
 
 ### Admin
 
-- Deploying a production server
+- Deploying to production
+
+  - [Setting up authentication](./config/authentication.md)
+  - [Configuring a database](./config/database.md)
   - [Deploying with Docker](../deployment/docker.md)
   - [Deploying with Kubernetes](../deployment/k8s.md)
-  - [Deploying with AWS Lightsail](../deployment/backstage-deploy/aws.md)
+
 - Configuring Backstage
-  - [Database](./config/database.md)
-  - [Authentication](./config/authentication.md)
-  - [Plugins](./configure-app-with-plugins.md)
-  - [Theme](./app-custom-theme.md)
-  - [Homepage](./homepage.md)
+
+  - [Adding plugins](./configure-app-with-plugins.md)
+  - [Customizing the theme](./app-custom-theme.md)
+  - [Populating the homepage](./homepage.md)
 
 ### Developer
 

docs/integrations/bitbucketServer/discovery--old.md

@@ -1,5 +1,5 @@
 ---
-id: discovery
+id: discovery--old
 title: Bitbucket Server Discovery
 sidebar_label: Discovery
 # prettier-ignore

docs/integrations/gitlab/discovery.md

@@ -150,6 +150,7 @@ catalog:
         branch: main # Optional. Used to discover on a specific branch
         fallbackBranch: master # Optional. Fallback to be used if there is no default branch configured at the Gitlab repository. It is only used, if `branch` is undefined. Uses `master` as default
         skipForkedRepos: false # Optional. If the project is a fork, skip repository
+        includeArchivedRepos: false # Optional. If project is archived, include repository
         group: example-group # Optional. Group and subgroup (if needed) to look for repositories. If not present the whole instance will be scanned
         entityFilename: catalog-info.yaml # Optional. Defaults to `catalog-info.yaml`
         projectPattern: '[\s\S]*' # Optional. Filters found projects based on provided patter. Defaults to `[\s\S]*`, which means to not filter anything
@@ -212,3 +213,5 @@ catalog:
 If you don't want create location object if file with component definition do not exists in project, you can set the `skipReposWithoutExactFileMatch` option. That can reduce count of request to gitlab with 404 status code.
 
 If you don't want to create location object if the project is a fork, you can set the `skipForkedRepos` option.
+
+If you want to create location object if the project is archived, you can set the `includeArchivedRepos` option.

docs/tooling/cli/03-commands.md

@@ -92,9 +92,11 @@ Usage: backstage-cli repo lint [options]
 Lint all packages in the project
 
 Options:
-  --format <format>  Lint report output format (default: "eslint-formatter-friendly")
-  --since <ref>      Only lint packages that changed since the specified ref
-  --fix              Attempt to automatically fix violations
+  --format <format>         Lint report output format (default: "eslint-formatter-friendly")
+  --since <ref>             Only lint packages that changed since the specified ref
+  --successCache            Enable success caching, which skips running tests for unchanged packages that were successful in the previous run
+  --successCacheDir <path>  Set the success cache location, (default: node_modules/.cache/backstage-cli)
+  --fix                     Attempt to automatically fix violations
 ```
 
 ## repo test
@@ -185,8 +187,9 @@ Usage: backstage-cli package lint [options]
 Lint a package
 
 Options:
-  --format <format>  Lint report output format (default: "eslint-formatter-friendly")
-  --fix              Attempt to automatically fix violations
+  --format <format>        Lint report output format (default: "eslint-formatter-friendly")
+  --fix                    Attempt to automatically fix violations
+  --max-warnings <number>  Fail if more than this number of warnings. -1 allows warnings. (default: 0)
 ```
 
 ## package test