Bumps Harbor version, syncs checksums, confirms directories

instruqt/closing-information-gap/01-viewing-instance-info/assignment.md

@@ -1,6 +1,6 @@
 ---
 slug: viewing-instance-info
-id: u7arnjksadrw
+id: jn2jgj1wc3e2
 type: challenge
 title: Getting a Picture of a Customer Instance
 teaser: Using the Replicated Platform to understand details of a customer instance

instruqt/closing-information-gap/02-working-with-support-bundles/assignment.md

@@ -1,6 +1,6 @@
 ---
 slug: working-with-support-bundles
-id: y9cpyp05iq1k
+id: yoaffx6a7m6t
 type: challenge
 title: Working with Support Bundles
 teaser: |-

instruqt/closing-information-gap/03-additional-information/assignment.md

@@ -1,6 +1,6 @@
 ---
 slug: additional-information
-id: sxl90k6n2bmz
+id: s124teq511sr
 type: challenge
 title: Collecting and Analyzing Additional Information
 teaser: |

instruqt/closing-information-gap/04-adding-to-the-chart/assignment.md

@@ -1,6 +1,6 @@
 ---
 slug: adding-to-the-chart
-id: vvxrunt3e7zu
+id: eyurng2zyce6
 type: challenge
 title: Adding the Support Bundle to the Harbor Helm Chart
 teaser: Learn how to incorporate your support bundle into your chart
@@ -129,7 +129,7 @@ Repackaging Your Chart
 ======================
 
 To distribute your support bundle, you should bump the version number in
-`harbor/Chart.yaml` (from `16.8.0` to `16.9.0`) adn then repackage it. You can edit
+`harbor/Chart.yaml` (from `19.3.0` to `16.9.0`) adn then repackage it. You can edit
 the version in the Manifest Editor or run the following command to do it from
 the shell.
 

instruqt/closing-information-gap/05-releasing-an-update/assignment.md

@@ -1,6 +1,6 @@
 ---
 slug: releasing-an-update
-id: tnyktndlfuw7
+id: phzx2xp3gdbp
 type: challenge
 title: Releasing an Update with the Support Bundle
 teaser: Releasing a new version with the support bundle included

instruqt/closing-information-gap/06-support-bundle-diagnosis/assignment.md

@@ -1,6 +1,6 @@
 ---
 slug: support-bundle-diagnosis
-id: y5uwhsz4tiwj
+id: ko5ke8j1aoto
 type: challenge
 title: Using the Support Bundle to Diagnose the Issue
 teaser: Discover the cause of Geeglo's outage using a support bundle

instruqt/closing-information-gap/07-other-ways/assignment.md

@@ -1,6 +1,6 @@
 ---
 slug: other-ways
-id: dfec8ytv6wmo
+id: zphzf0yxstck
 type: challenge
 title: Other Ways to Offer a Support Bundle
 teaser: Explore other ways to distibute your support bundle and keep it up to date

instruqt/closing-information-gap/track.yml

@@ -1,5 +1,5 @@
 slug: closing-information-gap
-id: 
+id: hfb41xqkyx0q
 title: Closing the Support Information Gap
 teaser: |-
   Use the Replicated Platform to close the information gap between your
@@ -19,16 +19,15 @@ description: |-
      issue multiple times
 icon: https://storage.googleapis.com/shared-lab-assets/icons/red/audit_log.png
 tags:
+- prod
 - builders-plan
-- helm
 - troubleshoot
-- prod
+- helm
 owner: replicated
 developers:
 - [email protected]
-maintenance: false
 lab_config:
   overlay: false
   width: 33
   position: right
-checksum: "8657597645467563973"
+checksum: "11287051276948358833"

instruqt/closing-information-gap/track_scripts/setup-shell

@@ -33,9 +33,10 @@ export REPLICATED_APP=${app_slug}
 
 ## release the application with the Replicated SDK
 cd /home/replicant
-mkdir release
-helm pull --version 16.6.8 oci://registry-1.docker.io/bitnamicharts/harbor --untar
-yq -i '.version = "16.7.0"' harbor/Chart.yaml
+mkdir /home/replicant/release
+
+helm pull --version 19.1.0 oci://registry-1.docker.io/bitnamicharts/harbor --untar
+yq -i '.version = "19.2.0"' harbor/Chart.yaml
 replicated_sdk_version=$(curl -qsfL https://api.github.com/repos/replicatedhq/replicated-sdk/tags | jq -r '.[0] | .name')
 yq -i ".dependencies += { \"name\": \"replicated\", \"repository\": \"oci://registry.replicated.com/library\", \"version\": \"${replicated_sdk_version#?}\"}" harbor/Chart.yaml
 
@@ -48,20 +49,20 @@ helm package harbor --destination release
 ## release and promote the app with the SDK added
 
 # release to the `Unstable` channel
-replicated release create --promote Unstable --yaml-dir /home/replicant/release --version 16.7.0 \
+replicated release create --promote Unstable --yaml-dir /home/replicant/release --version 19.2.0 \
   --release-notes "Prepares for distribution with Replicated by incorporating the Replicated SDK" \
   --app ${app_slug} --token ${api_token}
 
 # get the sequence number for the release to promote
 release_sequence=$(curl --header "Accept: application/json" --header "Authorization: ${api_token}" https://api.replicated.com/vendor/v3/apps | jq -r '.apps[0].channels[] | select( .name == "Unstable" ) | .releaseSequence')
 
 # promote to the `Beta` channel
-replicated release promote ${release_sequence} Beta --version 16.7.0 \
+replicated release promote ${release_sequence} Beta --version 19.2.0 \
   --release-notes "Prepares for distribution with Replicated by incorporating the Replicated SDK" \
   --app ${app_slug} --token ${api_token}
 
 # promote to the `Stable` channel
-replicated release promote ${release_sequence} Stable --version 16.7.0 \
+replicated release promote ${release_sequence} Stable --version 19.2.0 \
   --release-notes "Prepares for distribution with Replicated by incorporating the Replicated SDK" \
   --app ${app_slug} --token ${api_token}
 
@@ -70,7 +71,7 @@ replicated channel create --name LTS --description "Releases with long-term supp
   --app ${app_slug} --token ${api_token}
 
 # remove the helm chart we used to create the release
-rm /home/replicant/release/harbor-16.7.0.tgz
+rm /home/replicant/release/harbor-19.2.0.tgz
 
 ## release the application with the Replicated SDK
 # add preflight checks to the Helm chart
@@ -158,32 +159,32 @@ stringData:
 HARBOR_PREFLIGHTS
 
 # bump the version
-yq -i '.version = "16.8.0"' /home/replicant/harbor/Chart.yaml
+yq -i '.version = "19.3.0"' /home/replicant/harbor/Chart.yaml
 helm package /home/replicant/harbor --destination /home/replicant/release
 chown -R replicant /home/replicant/harbor /home/replicant/release
 
 ## release and promote the preflight checks added
 
 # release to the `Unstable` channel
-replicated release create --promote Unstable --yaml-dir /home/replicant/release --version 16.8.0 \
+replicated release create --promote Unstable --yaml-dir /home/replicant/release --version 19.3.0 \
   --release-notes "Adds preflight checks to enable customers to validate cluster prerequisites before installing" \
   --app ${app_slug} --token ${api_token}
 
 # get the sequence number for the release to promote
 release_sequence=$(curl --header "Accept: application/json" --header "Authorization: ${api_token}" https://api.replicated.com/vendor/v3/apps | jq -r '.apps[0].channels[] | select( .name == "Unstable" ) | .releaseSequence')
 
 # promote to the `Beta` channel
-replicated release promote ${release_sequence} Beta --version 16.8.0 \
+replicated release promote ${release_sequence} Beta --version 19.3.0 \
   --release-notes "Adds preflight checks to enable customers to validate cluster prerequisites before installing" \
   --app ${app_slug} --token ${api_token}
 
 # promote to the `Stable` channel
-replicated release promote ${release_sequence} Stable --version 16.8.0 \
+replicated release promote ${release_sequence} Stable --version 19.3.0 \
   --release-notes "Adds preflight checks to enable customers to validate cluster prerequisites before installing" \
   --app ${app_slug} --token ${api_token}
 
 # remove the helm chart we used to create the release
-rm /home/replicant/release/harbor-16.8.0.tgz
+rm /home/replicant/release/harbor-19.3.0.tgz
 
 ## create the customer from the preflights lab
 
@@ -216,7 +217,7 @@ helm registry login registry.replicated.com \
 # install the application, trying again if it fails since there might be timing issues
 set +e
 retries=0
-while ! helm install harbor --version 16.8.0 \
+while ! helm install harbor --version 19.3.0 \
   oci://registry.replicated.com/${app_slug}/harbor \
   --set service.type=NodePort --set service.nodePort.https=30443 \
   --set externalURL=https://cluster-30443-${INSTRUQT_PARTICIPANT_ID}.env.play.instruqt.com \