fix/docs reverting (#1663)

* Revert "Docs: restructure to Team and EE tabs"

This reverts commit 5e8fdf5.

* fix docs quickstart and broken links

Author: motatoes

docs/ce/cloud-providers/authenticating-with-oidc-on-aws.mdx

@@ -5,21 +5,36 @@ title: "Authenticating with OIDC on AWS"
 In order to set up OIDC simply swap the AWS Keys with assume role ARN and you are good to go. Here is an example, don't forget to replace the line starting in \*\* with your own ARN for the account.
 
 ```
-...
+name: Digger Workflow
 
-jobs:
-  digger-job:
+on:
+  workflow_dispatch:
+    inputs:
+      run_name:
+        required: false
+      spec:
+        required: true
+
+run-name: '${{inputs.run_name}}'
 
-    ...
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write      # required to merge PRs
+      id-token: write      # required for workload-identity-federation
+      pull-requests: write # required to post PR comments
+      statuses: write      # required to validate combined PR status
 
     steps:
       - name: digger run
         uses: diggerhq/digger@vLatest
         with:
+          digger-spec: ${{ inputs.spec }}
           setup-aws: true
-          aws-role-to-assume: arn:aws:iam::{AccountID}:role/{RoleName}
+        **aws-role-to-assume: arn:aws:iam::{AccountID}:role/{RoleName}**
           aws-region: us-east-1
-
-    ...
-
+        env:
+          GITHUB_CONTEXT: ${{ toJson(github) }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 ```

docs/ce/features/plan-persistence.mdx

@@ -2,4 +2,4 @@
 title: "Plan Persistence"
 ---
 
-By default digger will run an apply based on the branch pull request files (no artefacts stored). In order to configure plan artefacts you can configure the inputs for storing as github artefacts or aws buckets or gcp buckets. The corresponding artefacts to be configured can be found in [storing plans in a bucket](/howto/store-plans-in-a-bucket)
+By default digger will run an apply based on the branch pull request files (no artefacts stored). In order to configure plan artefacts you can configure the inputs for storing as github artefacts or aws buckets or gcp buckets. The corresponding artefacts to be configured can be found in [storing plans in a bucket](/ce/howto/store-plans-in-a-bucket)

docs/ce/getting-started/github-actions-+-aws.mdx

@@ -43,16 +43,11 @@ name: Digger Workflow
 
 on:
   workflow_dispatch:
-  inputs:
-    id:
-      description: 'run identifier'
-      required: false
-    job:
-      required: true
-    comment_id:
-      required: true
-    run_name:
-      required: false
+    inputs:
+      spec:
+        required: true
+      run_name:
+        required: false
 
 run-name: '${{inputs.run_name}}'
 
@@ -68,14 +63,14 @@ jobs:
 
     steps:
       - uses: actions/checkout@v4
-      - name: ${{github.event.inputs.id}}
-        run: echo job id ${{ inputs.id }}
+      - name: ${{ fromJSON(github.event.inputs.spec).job_id }}
+        run: echo "job id ${{ fromJSON(github.event.inputs.spec).job_id }}"
       - uses: diggerhq/digger@vLatest
         with:
+          digger-spec: ${{ inputs.spec }}
           setup-aws: true
           aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
           aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-          disable-locking: true
         env:
           GITHUB_CONTEXT: ${{ toJson(github) }}
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

docs/ce/getting-started/github-actions-and-gcp.mdx

@@ -43,12 +43,7 @@ name: Digger
 on:
   workflow_dispatch:
     inputs:
-      id:
-        description: 'run identifier'
-        required: false
-      job:
-        required: true
-      comment_id:
+      spec:
         required: true
       run_name:
         required: false
@@ -67,8 +62,8 @@ jobs:
       statuses: write      # required to validate combined PR status
     steps:
     - uses: actions/checkout@v4
-    - name: ${{github.event.inputs.id}}
-      run: echo job id ${{ inputs.id }}
+    - name: ${{ fromJSON(github.event.inputs.spec).job_id }}
+      run: echo "job id ${{ fromJSON(github.event.inputs.spec).job_id }}"
     - id: 'auth'
       uses: 'google-github-actions/auth@v1'
       with:
@@ -81,8 +76,8 @@ jobs:
     - name: digger run
         uses: diggerhq/digger@vLatest
         with:
+          digger-spec: ${{ inputs.spec }}
           setup-aws: false
-          disable-locking: true
         env:
           GITHUB_CONTEXT: ${{ toJson(github) }}
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

docs/ce/howto/backendless-mode.mdx

@@ -5,7 +5,7 @@ title: "Backendless mode"
 Digger works best as a 2-piece solution:
 
 - a CLI that runs inside your CI
-- an orchestrator backend that triggers the CI jobs ([GitHub App](https://dashboard.digger.dev) or [self-hosted](/self-host/deploy-docker))
+- an orchestrator backend that triggers the CI jobs ([GitHub App](https://dashboard.digger.dev) or [self-hosted](/ce/self-host/deploy-docker))
 
 You can however still use the most basic features of Digger as a standalone action without a backend. To do that, set the following option in your workflow configuration:
 

docs/ce/howto/custom-commands.mdx

@@ -27,7 +27,7 @@ Digger makes the following environment variables available to custom commands:
 - `$PR_BRANCH`
 - `$PROJECT_NAME`
 
-These can be used to achieve workflows like [infracost diff](/howto/using-infracost)
+These can be used to achieve workflows like [infracost diff](/ce/howto/using-infracost)
 
 ## $DIGGER_OUT
 

docs/ce/howto/disable-locking.mdx

@@ -0,0 +1,13 @@
+---
+title: "Disable locking"
+---
+
+In order to disable locking repo wide you can add a top-level flag to your digger.yml:
+
+```
+pr_locks: false
+
+projects:
+   - name: dev
+     dir: dev/
+```

docs/ce/howto/multiacc-aws.mdx

@@ -49,12 +49,7 @@ name: Digger Workflow
 on:
   workflow_dispatch:
   inputs:
-    id:
-      description: 'run identifier'
-      required: false
-    job:
-      required: true
-    comment_id:
+    spec:
       required: true
     run_name:
       required: false
@@ -74,14 +69,14 @@ jobs:
 
     steps:
       - uses: actions/checkout@v4
-      - name: ${{github.event.inputs.id}}
-        run: echo job id ${{ inputs.id }}
+      - name: ${{ fromJSON(github.event.inputs.spec).job_id }}
+        run: echo "job id ${{ fromJSON(github.event.inputs.spec).job_id }}"
       - uses: diggerhq/digger@vLatest
         with:
+          digger-spec: ${{ inputs.spec }}
           setup-aws: true
           aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
           aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-          disable-locking: true
         env:
           GITHUB_CONTEXT: ${{ toJson(github) }}
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

docs/ce/howto/project-level-roles.mdx

@@ -36,7 +36,7 @@ parameter within the workflow file. This role needs to have ability to assume al
 If you are not using a aws-role-to-assume setting it workflow you **must** add ```AwsRoleRegion``` property to project level ```aws_role_to_assume```
 </Note>
 
-You can also use project-level assume role with [generated projects](/howto/generate-projects):
+You can also use project-level assume role with [generated projects](/ce/howto/generate-projects):
 
 ```
 generate_projects:

docs/ce/howto/using-checkov.mdx

@@ -18,4 +18,4 @@ workflows:
         - run: checkov -d . --framework terraform
 ```
 
-<Note>This docs page needs improvement. Please consider contributing to [docs](https://github.com/diggerhq/docs). Here is the [relevant PR](https://github.com/diggerhq/digger/pull/267) implementing this feature</Note>
+<Note>This docs page needs improvement. Please consider contributing to [docs](https://github.com/diggerhq/digger/tree/develop/docs). Here is the [relevant PR](https://github.com/diggerhq/digger/pull/267) implementing this feature</Note>