Get versions in docs from release repo.

Author: Gerrit91

.github/workflows/deploy.yaml

@@ -24,4 +24,4 @@ jobs:
       - name: Build and deploy
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: julia --color=yes --project=docs/ -e 'using Pkg; Pkg.instantiate(); include("docs/make.jl")'
+        run: julia --color=yes --project=docs/ -e 'using Pkg; Pkg.develop(PackageSpec(path="/workdir")); Pkg.resolve(); include("docs/make.jl")'

Makefile

@@ -3,4 +3,4 @@
 .PHONY: build
 build:
 	docker build -t docs-builder .
-	docker run -it --rm -v $(PWD)/docs:/workdir/docs -w /workdir docs-builder julia --color=yes --project=docs/ -e 'using Pkg; Pkg.instantiate(); include("docs/make.jl")'
+	docker run -it --rm -v $(PWD)/docs:/workdir/docs -w /workdir docs-builder julia --color=yes --project=docs/ -e 'using Pkg; Pkg.develop(PackageSpec(path="/workdir")); Pkg.resolve(); include("docs/make.jl")'

Project.toml

@@ -1,3 +1,9 @@
 name = "Docs"
 uuid = "e1c13cdf-5c0d-472c-a597-c85aecc67ad6"
 version = "0.1.0"
+
+[deps]
+HTTP = "cd3eb016-35fb-5094-929b-558a96fad6f3"
+YAML = "ddb6d928-2868-570f-bddf-ab3f9cf99eb6"
+Markdown = "d6f4376e-aef5-505a-96c1-9c027394607a"
+Printf = "de0858da-6303-5e67-8744-51eddeeeb8d7"

docs/Manifest.toml

@@ -17,12 +17,30 @@ git-tree-sha1 = "88bb0edb352b16608036faadcc071adda068582a"
 uuid = "ffbed154-4ef7-542d-bbb7-c09d3a79fcae"
 version = "0.8.1"
 
+[[Docs]]
+deps = ["HTTP", "Markdown", "Printf", "YAML"]
+path = "/workdir"
+uuid = "e1c13cdf-5c0d-472c-a597-c85aecc67ad6"
+version = "0.1.0"
+
 [[Documenter]]
 deps = ["Base64", "Dates", "DocStringExtensions", "InteractiveUtils", "JSON", "LibGit2", "Logging", "Markdown", "REPL", "Test", "Unicode"]
 git-tree-sha1 = "395fa1554c69735802bba37d9e7d9586fd44326c"
 uuid = "e30172f5-a6a5-5a46-863b-614d45cd2de4"
 version = "0.24.11"
 
+[[HTTP]]
+deps = ["Base64", "Dates", "IniFile", "MbedTLS", "Sockets"]
+git-tree-sha1 = "ec87d5e2acbe1693789efbbe14f5ea7525758f71"
+uuid = "cd3eb016-35fb-5094-929b-558a96fad6f3"
+version = "0.8.15"
+
+[[IniFile]]
+deps = ["Test"]
+git-tree-sha1 = "098e4d2c533924c921f9f9847274f2ad89e018b8"
+uuid = "83e8ac13-25f8-5344-8a64-a9f2b223428f"
+version = "0.5.0"
+
 [[InteractiveUtils]]
 deps = ["Markdown"]
 uuid = "b77e0a4c-d291-57a0-90e8-8db25a27a240"
@@ -47,6 +65,18 @@ uuid = "56ddb016-857b-54e1-b83d-db4d58db5568"
 deps = ["Base64"]
 uuid = "d6f4376e-aef5-505a-96c1-9c027394607a"
 
+[[MbedTLS]]
+deps = ["Dates", "MbedTLS_jll", "Random", "Sockets"]
+git-tree-sha1 = "426a6978b03a97ceb7ead77775a1da066343ec6e"
+uuid = "739be429-bea8-5141-9913-cc70e7f3736d"
+version = "1.0.2"
+
+[[MbedTLS_jll]]
+deps = ["Libdl", "Pkg"]
+git-tree-sha1 = "c83f5a1d038f034ad0549f9ee4d5fac3fb429e33"
+uuid = "c8ffd9c3-330d-5841-b78e-0817d7145fa1"
+version = "2.16.0+2"
+
 [[Mmap]]
 uuid = "a63ad114-7e13-5084-954f-fe012c677804"
 
@@ -91,3 +121,9 @@ uuid = "cf7118a7-6976-5b1a-9a39-7adc72f591a4"
 
 [[Unicode]]
 uuid = "4ec0a83e-493e-50e2-b9ac-8f72acf5a8f5"
+
+[[YAML]]
+deps = ["Base64", "Dates", "Printf"]
+git-tree-sha1 = "c5e2eaa5ce818c5277388377d592eb4c81f27c00"
+uuid = "ddb6d928-2868-570f-bddf-ab3f9cf99eb6"
+version = "0.4.0"

docs/Project.toml

@@ -1,4 +1,5 @@
 [deps]
+Docs = "e1c13cdf-5c0d-472c-a597-c85aecc67ad6"
 Documenter = "e30172f5-a6a5-5a46-863b-614d45cd2de4"
 
 [compat]

docs/src/index.md

@@ -37,7 +37,7 @@ Not only does the metal-stack run smoothly on [Kubernetes](https://kubernetes.io
 
 From the perspective of the Gardener, the metal-stack is just another cloud provider. The time savings compared to providing machines and Kubernetes by hand are significant. We actually want to be able to compete with offers of public cloud providers, especially regarding speed and usability.
 
-Of course, you can use metal-stack only for machine provisioning as well and just put something else on top of the metal infrastructure. 
+Of course, you can use metal-stack only for machine provisioning as well and just put something else on top of the metal infrastructure.
 
 ### Open Source
 

docs/src/installation/deployment.md

@@ -60,15 +60,26 @@ Let's now create the following files and folder structures:
 
 The `requirements.yaml` is used for declaring [Ansible Galaxy](https://galaxy.ansible.com/) role depedencies. It will dynamically provide the [metal-roles](https://github.com/metal-stack/metal-roles) and the [ansible-common](https://github.com/metal-stack/ansible-common) role when starting the deployment. The file should contain the following dependencies:
 
+````@eval
+using Docs
+
+ansible_common = releaseVector()["ansible-roles"]["ansible-common"]["version"]
+metal_roles = releaseVector()["ansible-roles"]["metal-roles"]["version"]
+
+t = """
 ```yaml
 ---
 - src: https://github.com/metal-stack/ansible-common.git
   name: ansible-common
-  version: v0.5.2
+  version: %s
 - src: https://github.com/metal-stack/metal-roles.git
   name: metal-roles
-  version: v0.1.12
+  version: %s
 ```
+"""
+
+printMarkdown(t, ansible_common, metal_roles)
+````
 
 !!! tip
 
@@ -147,21 +158,21 @@ Basically, this playbook does the following:
 
 Next you will need to parametrize the referenced roles to fit your requirements. The variables of the role dependencies can be looked up in the role documention on [metal-roles/control-plane](https://github.com/metal-stack/metal-roles/tree/master/control-plane). You should not need to define a lot of variables here for now, most values are reasonably defaulted in the roles. Just make sure you define all the "required" variables in your `group_vars/control-plane/all.yaml`, which looks like this:
 
+````@eval
+using Docs
+
+t = """
 ```yaml
 ---
 # common defaults
 metal_control_plane_ingress_dns: <your-dns-domain> # if you are trying this with a local setup, you can consider using xip.io
 
-# image versions
-metal_api_image_tag: v0.7.5
-metal_metalctl_image_tag: v0.7.5
-metal_masterdata_api_image_tag: v0.7.1
-metal_console_image_tag: v0.4.1
-
-metal_db_backup_restore_sidecar_image_tag: v0.5.1
-ipam_db_backup_restore_sidecar_image_tag: v0.5.1
-masterdata_db_backup_restore_sidecar_image_tag: v0.5.1
+metal_stack_version: %s
 ```
+"""
+
+printMarkdown(t, releaseVersion())
+````
 
 By the time you will certainly add more parametrization to the deployment. When this happens, feel free to split up your `all.yaml` into separate files to keep everything nice and pretty.
 
@@ -182,20 +193,30 @@ This is how your `roles/ingress-controller/tasks/main.yaml` could look like:
 
 Now, it should be possible to run the deployment through a Docker container. Make sure to have the [Kubeconfig file](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) of your cluster and set the path in the following command accordingly:
 
+````@eval
+using Docs
+
+base_image = releaseVector()["docker-images"]["metal-stack"]["generic"]["deployment-base"]["tag"]
+
+t = raw"""
 ```bash
 export KUBECONFIG=<path-to-your-cluster-kubeconfig>
 docker run --rm -it \
   -v $(pwd):/workdir \
   --workdir /workdir \
   -e KUBECONFIG="${KUBECONFIG}" \
   -e K8S_AUTH_KUBECONFIG="${KUBECONFIG}" \
-  metalstack/metal-deployment-base:v0.0.5 \
+  metalstack/metal-deployment-base:%s \
   /bin/bash -ce \
     "ansible-galaxy install -r requirements.yaml
     ansible-playbook \
       -i inventories/control-plane.yaml \
       deploy_metal_control_plane.yaml"
 ```
+"""
+
+printMarkdown(t, base_image)
+````
 
 !!! tip
 

src/Docs.jl

@@ -1,3 +1,17 @@
 module Docs
+    using YAML, HTTP, Markdown, Printf
 
+    export releaseVersion, releaseVector, printMarkdown
+
+    releaseVersion() = "master"
+    releaseVector() = release_vector
+
+    r = HTTP.request("GET", string("https://raw.githubusercontent.com/metal-stack/releases/", releaseVersion(), "/release.yaml"))
+    release_vector = YAML.load(String(r.body))
+
+    constsprintf(fmt::String,args...) = @eval @sprintf($fmt,$(args...))
+
+    function printMarkdown(t, x...)
+        return Markdown.parse(constsprintf(t, x...))
+    end
 end