Merge branch 'main' into rm/compress-vagrant-images

Author: rmainwork

.github/actions/reload-dev-portal/action.yml

@@ -51,11 +51,8 @@ jobs:
       - name: Deploy Project Artifacts to Vercel
         run: vercel deploy --prebuilt --prod --token=${{ secrets.VERCEL_TOKEN }} --logs --archive=tgz
 
-      - name: Reload dev portal on changed files
-        uses: ./.github/actions/reload-dev-portal
-        with:
-          base_sha: ${{ github.event.before }}
-          head_sha: ${{ github.event.after }}
-          dev-portal-deploy-hook-prod: ${{ secrets.DEV_PORTAL_DEPLOY_HOOK_PROD }}
-          revalidate-token: ${{ secrets.REVALIDATE_TOKEN }}
-          bot-bypass-token: ${{ secrets.DEVELOPER_BOT_BYPASS_TOKEN }}  
+      - name: Rebuild Dev Portal
+        shell: bash
+        run: |
+          echo "Rebuilding all of dev-portal"
+          curl -X POST ${{ secrets.DEV_PORTAL_DEPLOY_HOOK_PROD }}

.github/workflows/deploy-udr.yml

@@ -0,0 +1,14 @@
+name: Force Rebuild Dev Portal
+
+on:
+  workflow_dispatch:
+
+jobs:
+  rebuild-dev-portal:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Rebuild Dev Portal
+        shell: bash
+        run: |
+          echo "Rebuilding all of dev-portal"
+          curl -X POST ${{ secrets.DEV_PORTAL_DEPLOY_HOOK_PROD }}

.github/workflows/force-rebuild-dev-portal.yml

@@ -68,4 +68,7 @@
 /content/vagrant @hashicorp/Vagrant
 
 # Nomad
-/content/nomad/ @hashicorp/nomad-docs @hashicorp/nomad-eng 
+/content/nomad/ @hashicorp/nomad-docs @hashicorp/nomad-eng 
+
+# Packer
+/content/packer @hashicorp/team-docs-packer-and-terraform @hashicorp/packer

.github/workflows/force-reload-dev-portal.yml

@@ -304,34 +304,125 @@ Before you can start Boundary, you must initialize the database from one Boundar
 Initialization is a one-time operation that executes the required database migrations for the Boundary cluster to operate.
 
 ```shell-session
-boundary database init -config /etc/boundary.d/controller.hcl
+$ boundary database init -config /etc/boundary.d/controller.hcl
 ```
 
-Unless you configure it not to, Boundary automatically generates a number of resources to make getting started easier. It automatically generates default scopes, auth methods, user, account, and targets. These
-resources, however, are not required. You can add the following flags to skip creating these initial resources:
+Boundary automatically generates a number of resources to make getting started easier unless you specify not to. Initializing the database automatically generates default scopes, auth methods, user, account, and targets. These resources are not required.
+
+You can add the following flags to skip creating these initial resources:
 
 ```shell-session
-boundary database init \
+$ boundary database init \
    -skip-auth-method-creation \
    -skip-host-resources-creation \
    -skip-scopes-creation \
    -skip-target-creation \
    -config /etc/boundary.d/controller.hcl
 ```
 
-Use the following command to view the help for additional initialization options:
+Use the following command to view the help for more initialization options:
 
 ```shell-session
-boundary database init -h
+$ boundary database init -h
 ```
 
 ## Start the Boundary service
 
 When the configuration files are in place on each Boundary controller, you can proceed to enable and start the binary on each of the Boundary controller nodes using `systemd`.
-Run the following commands to start the service:
 
-1. `sudo systemctl enable boundary`
-1. `sudo systemctl start boundary`
+Run the following commands to enable and start the service:
+
+1. 
+
+  ```shell-session
+  $ sudo systemctl enable boundary
+  ```
+
+1.
+
+  ```shell-session
+  $ sudo systemctl start boundary
+  ```
+
+## Manually configure systemd (optional)
+
+If you [installed Boundary manually](/boundary/docs/deploy/self-managed/install#manually-install-boundary), you can configure Boundary to run as a service under systemd. 
+
+To do this, you should:
+
+1. Check the location of your controller configuration file on disk, such as `/etc/boundary.d/controller.hcl` in the example on this page. You will need to reference the location to the .hcl configuration file when you set up the unit file in the next steps.
+1. Configure the user and group the Boundary service runs under.
+1. Set up the systemd unit file.
+1. Start the Boundary service.
+
+### Configure the user and group
+
+HashiCorp recommends running Boundary as a non-root user and managing the Boundary process running under systemd with this user.
+
+Add the `boundary` system user and group to ensure you have a no-login user that owns and runs Boundary:
+
+```shell-session
+$ sudo adduser --system --group boundary || true ;
+$ sudo chown boundary:boundary /etc/boundary.d/controller.hcl ;
+$ sudo chown boundary:boundary /usr/local/bin/boundary
+```
+
+<Tip>
+
+Make sure to [initialize the database](#initialize-the-database) before starting the service. If another controller or worker has already done this, you will receive an expected error stating that the database has already been initialized.
+
+</Tip>
+
+### Set up the unit file
+
+Create a new unit file, such as `/etc/systemd/system/boundary-controller.service`. Add the following code to the file. Update the path to your `controller.hcl` file on the `ExecStart` line, and the user and group as needed.
+
+<CodeBlockConfig filename="/etc/systemd/system/boundary-controller.service">
+
+```bash
+[Unit]
+Description="HashiCorp Boundary controller"
+Documentation=https://developer.hashicorp.com/boundary/docs
+StartLimitIntervalSec=60
+StartLimitBurst=3
+
+[Service]
+EnvironmentFile=-/etc/boundary.d/boundary.env
+User=boundary
+Group=boundary
+ProtectSystem=full
+ProtectHome=read-only
+ExecStart=/usr/bin/boundary server -config=/etc/boundary.d/controller.hcl
+ExecReload=/bin/kill --signal HUP $MAINPID
+KillMode=process
+KillSignal=SIGINT
+Restart=on-failure
+RestartSec=5
+TimeoutStopSec=30
+LimitMEMLOCK=infinity
+
+[Install]
+WantedBy=multi-user.target
+EOF
+```
+
+</CodeBlockConfig>
+
+### Start the Boundary service
+
+Set the appropriate permissions on the unit file:
+
+```shell-session
+$ sudo chmod 664 /etc/systemd/system/boundary-controller.service
+```
+
+Reload the systemd daemon, and enable and start the Boundary service:
+
+```shell-session
+$ sudo systemctl daemon-reload ;
+$ sudo systemctl enable boundary-controller ;
+$ sudo systemctl start boundary-controller
+```
 
 ## Authenticate and manage resources