From eb93343ffe024542c4a7c54b60a35b4739da3bba Mon Sep 17 00:00:00 2001
From: Robert Fairburn <8029478+rfairburn@users.noreply.github.com>
Date: Tue, 25 Apr 2023 13:22:59 -0500
Subject: [PATCH] Warn against deploying fleetdm/fleet:main directly (#11316)

Deploying `fleetdm/fleet:main` directly to dogfood has problems if
migrations are needed and an image restarts. This causes crashloops in
the containers and leads to being rate-limited for pulls on dockerhub.
Warn against this and also suggest using quay.io as an alternative image
location.
---
 .github/workflows/dogfood-deploy.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/dogfood-deploy.yml b/.github/workflows/dogfood-deploy.yml
index 6c246944b3..47a7433cdc 100644
--- a/.github/workflows/dogfood-deploy.yml
+++ b/.github/workflows/dogfood-deploy.yml
@@ -4,7 +4,7 @@ on:
   workflow_dispatch:
     inputs:
       DOCKER_IMAGE:
-        description: 'The full name of the docker image to be deployed. (e.g. fleetdm/fleet:v4.30.0)'
+        description: 'The full name of the docker image to be deployed. (e.g. fleetdm/fleet:v4.30.0). Note: do not use fleetdm/fleet:main directly.  Use the short hash instead.  If pull-rate limited, try using the quay.io/fleetdm/fleet mirror.'
         required: true
 
 # This allows a subsequently queued workflow run to interrupt previous runs