Merge pull request #33065 from awanlin/docs/clean-up

[Doc] Removed Mentions of the New Backend System

docs/features/kubernetes/authenticationstrategy.md

@@ -157,7 +157,7 @@ export class AwsIamStrategy implements AuthenticationStrategy {
 
 Sometimes you need to add a new way to authenticate against a kubernetes cluster not support by default by Backstage. This is how integrators can bring their own kubernetes auth strategies through the use of the [`addAuthStrategy`](https://github.com/backstage/backstage/blob/57397e7d6d2d725712c439f4ab93f2ac6aa27bf8/plugins/kubernetes-backend/src/service/KubernetesBuilder.ts#L211) method on `KubernetesBuilder` or through the [AuthStrategyExtensionPoint](https://github.com/backstage/backstage/blob/57397e7d6d2d725712c439f4ab93f2ac6aa27bf8/plugins/kubernetes-backend/src/plugin.ts#L112). So, on the following sections, we are going to introduce a new AuthStrategy for [Pinniped][1], an authentication service for Kubernetes clusters.
 
-### Custom Pinniped auth strategy in the new backend system
+### Custom Pinniped auth strategy in the backend system
 
 To add a new AuthStrategy, we need to create a new Pinniped [backend module](../../backend-system/building-plugins-and-modules/01-index.md#modules) to extend the Kubernetes-Backend plugin. The Pinniped module will interact with the Kubernetes-Backend plugin through the [extension points](../../backend-system/architecture/05-extension-points.md) registered by the plugin. The Kubernetes-Backend plugin [registers](https://github.com/backstage/backstage/blob/ebe7afad9d19f279469168ca0d4feceb92c1ad36/plugins/kubernetes-backend/src/plugin.ts#L155) multiple extension points like `kubernetesObjectsProvider`, `kubernetesClusterSupplier`, `kubernetesFetcher`, `kubernetesServiceLocator` and the `kubernetesAuthStrategy`.
 

docs/features/software-templates/authorizing-scaffolder-template-details.md

@@ -6,7 +6,13 @@ description: How to authorize parts of a template and authorize scaffolder task
 
 The scaffolder plugin integrates with the Backstage [permission framework](../../permissions/overview.md), which allows you to control access to certain parameters and steps in your templates based on the user executing the template. It also allows you to control access to scaffolder tasks.
 
-### Authorizing parameters and steps
+:::tip
+
+To better understand the following examples make sure to review the [Writing a permission policy](../../permissions/writing-a-policy.md)) documentation before moving forward.
+
+:::
+
+## Authorizing parameters and steps
 
 To mark specific parameters or steps as requiring permission, add the `backstage:permissions` property to the parameter or step with one or more tags. For example:
 
@@ -288,62 +294,3 @@ All other users are granted permissions to perform/access the following actions/
 - Read scaffolder tasks and their associated events/logs for tasks created by the user.
 
 Although the rules exported by the scaffolder are simple, combining them can help you achieve more complex use cases.
-
-### Authorizing in the New Backend System
-
-Instead of the changes in `permission.ts` noted in the above example you will make them in your `index.ts`. You will need to create a module where your permission policy will get added. Here is a very simplified example of how to do that:
-
-```ts title="packages/backend/src/index.ts"
-import { createBackendModule } from '@backstage/backend-plugin-api';
-import {
-  PolicyDecision,
-  AuthorizeResult,
-} from '@backstage/plugin-permission-common';
-import {
-  PermissionPolicy,
-  PolicyQuery,
-  PolicyQueryUser,
-} from '@backstage/plugin-permission-node';
-import { policyExtensionPoint } from '@backstage/plugin-permission-node/alpha';
-
-class ExamplePermissionPolicy implements PermissionPolicy {
-  async handle(
-    request: PolicyQuery,
-    user?: PolicyQueryUser,
-  ): Promise<PolicyDecision> {
-    // Various scaffolder permission checks ...
-
-    return {
-      result: AuthorizeResult.ALLOW,
-    };
-  }
-}
-
-const customPermissionBackendModule = createBackendModule({
-  pluginId: 'permission',
-  moduleId: 'allow-all-policy',
-  register(reg) {
-    reg.registerInit({
-      deps: { policy: policyExtensionPoint },
-      async init({ policy }) {
-        policy.setPolicy(new ExamplePermissionPolicy());
-      },
-    });
-  },
-});
-
-const backend = createBackend();
-
-// Other plugins...
-
-/* highlight-add-start */
-backend.add(import('@backstage/plugin-permission-backend'));
-backend.add(customPermissionBackendModule);
-/* highlight-add-end */
-```
-
-:::note Note
-
-The `ExamplePermissionPolicy` here could be the one from the [Authorizing parameters and steps](#authorizing-parameters-and-steps) example or from the [Authorizing actions](#authorizing-actions) example. It would work the same way for both of them.
-
-:::

docs/features/software-templates/builtin-actions.md

@@ -32,7 +32,7 @@ Here's how to add an action module, first you need to run this command:
 yarn --cwd packages/backend add @backstage/plugin-scaffolder-backend-module-github
 ```
 
-Then you need to add it to your backend, this is a simplified new backend system for example purposes:
+Then you need to add it to your backend, this is a simplified backend system for example purposes:
 
 ```ts title="/packages/backend/src/index.ts"
 import { createBackend } from '@backstage/backend-defaults';

docs/features/techdocs/getting-started.md

@@ -95,9 +95,6 @@ That's it! Now, we need the TechDocs Backend plugin for the frontend to work.
 
 ## Adding TechDocs Backend plugin
 
-:::note
-These instructions are for the new backend system. For setting this up in the old backend system, see [here](https://github.com/backstage/backstage/blob/v1.36.1/docs/features/techdocs/getting-started.md)
-:::
 First we need to install the `@backstage/plugin-techdocs-backend` package.
 
 ```bash title="From your Backstage root directory"

docs/features/techdocs/how-to-guides.md

@@ -852,9 +852,9 @@ and publish the documentation for them. If the value of the `company.com/techdoc
 annotation is anything other than `'local'`, the user is responsible for publishing
 documentation to the appropriate location in the TechDocs external storage.
 
-### Hybrid build strategy using the New Backend System
+### Hybrid build strategy using the Backend System
 
-To setup a hybrid build strategy using the New Backend System you'll follow the same steps as above but for Step 4 you will need to do the following:
+To setup a hybrid build strategy using the Backend System you'll follow the same steps as above but for Step 4 you will need to do the following:
 
 ```ts title="packages/backend/src/index.ts"
 const backend = createBackend();