add hub.config passthrough and use it for all auth config

.github/workflows/test-chart.yaml

@@ -12,11 +12,13 @@ on:
       - "doc/**"
       - "**/test-docs.yaml"
       - "**.md"
+      - "**/schema.yaml"
   push:
     paths-ignore:
       - "doc/**"
       - "**/test-docs.yaml"
       - "**.md"
+      - "**/schema.yaml"
     branches-ignore:
       - "dependabot/**"
   workflow_dispatch:

.github/workflows/test-docs.yaml

@@ -9,10 +9,12 @@ on:
   pull_request:
     paths:
       - "doc/**"
+      - "**/schema.yaml"
       - "**/test-docs.yaml"
   push:
     paths:
       - "doc/**"
+      - "**/schema.yaml"
       - "**/test-docs.yaml"
     branches-ignore:
       - "dependabot/**"

doc/Makefile

@@ -27,7 +27,7 @@ help:
 # - builds and rebuilds html on changes to source
 # - starts a livereload enabled webserver and opens up a browser
 devenv:
-	sphinx-autobuild -b html --open-browser --ignore "*/reference.md" "$(SOURCEDIR)" "$(BUILDDIR)/html" $(SPHINXOPTS)
+	sphinx-autobuild -b html --open-browser --ignore "*/reference.md" --watch "../jupyterhub/schema.yaml" "$(SOURCEDIR)" "$(BUILDDIR)/html" $(SPHINXOPTS)
 
 # For local development and CI:
 # - verifies that links are valid

doc/make.bat

@@ -39,7 +39,7 @@ if errorlevel 9009 (
 	echo.The 'sphinx-autobuild' command was not found. Open and read README.md!
 	exit /b 1
 )
-sphinx-autobuild -b html --open-browser --ignore "*/reference.md" "%SOURCEDIR%" "%BUILDDIR%/html" %SPHINXOPTS%
+sphinx-autobuild -b html --open-browser --ignore "*/reference.md" --watch "../jupyterhub/schema.yaml" "%SOURCEDIR%" "%BUILDDIR%/html" %SPHINXOPTS%
 goto end
 
 

doc/source/administrator/advanced.md

@@ -201,7 +201,7 @@ The items in this list must be valid kubernetes
 ### Specifying suitable hub storage
 
 By default, the hub's sqlite-pvc setting will dynamically create a disk to store
-the sqlite database. It is possible to {ref}`configure other storage classes <schema:hub.db.type>`
+the sqlite database. It is possible to [configure other storage classes](schema_hub.db.type)
 under hub.db.pvc, but make sure
 to choose one that the hub can write quickly and safely to. Slow or higher
 latency storage classes can cause hub operations to lag which may ultimately