From 89659a05b3a0841abf2ef067c1175c0b31306540 Mon Sep 17 00:00:00 2001 From: YuviPanda Date: Mon, 4 Dec 2023 12:14:14 -0800 Subject: [PATCH] Add deleting cloud bucket data to decomission list --- .github/ISSUE_TEMPLATE/5_decommission-hub.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/5_decommission-hub.md b/.github/ISSUE_TEMPLATE/5_decommission-hub.md index c0fb1ae114..afd0e2f2ac 100644 --- a/.github/ISSUE_TEMPLATE/5_decommission-hub.md +++ b/.github/ISSUE_TEMPLATE/5_decommission-hub.md @@ -32,7 +32,8 @@ Usually, it is because it was a hub that we created for a workshop/conference an (These steps are described in more detail in the docs at https://infrastructure.2i2c.org/en/latest/hub-deployment-guide/hubs/other-hub-ops/delete-hub.html) -- [ ] Manage existing data (migrate data from the hub or delete it) +- [ ] Manage existing home directory data (migrate data from the hub or delete it) +- [ ] Manage existing cloud bucket data (migrate data, or delete it) - [ ] Delete the hub's authentication application on GitHub or CILogon (note CILogon removal requires the hub config in place) - [ ] Remove the appropriate `config/clusters//.values.yaml` files. A complete list of relevant files can be found under the appropriate entry in the associated `cluster.yaml` file. - [ ] Remove the associated hub entry from the `config/clusters//cluster.yaml` file.