Skip to content

Commit 193e187

Browse files
committed
Document needing hubspot deal ids
1 parent 44f4c34 commit 193e187

2 files changed

Lines changed: 14 additions & 0 deletions

File tree

.github/ISSUE_TEMPLATE/03_new-hub_phase-1.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,7 @@ body:
3434
| Name of cloud account | | |
3535
| Community Representative(s) (GitHub handles or email) | | |
3636
| Have the Technical Contacts been added to the [AirTable](https://airtable.com/appbjBTRIbgRiElkr/pagD3XyZjqBunYMnC)? | `Yes/No` | |
37+
| Hubspot Deal URL | | |
3738
3839
Available runbooks:
3940
- https://infrastructure.2i2c.org/hub-deployment-guide/runbooks/phase1/#available-runbooks

docs/hub-deployment-guide/new-cluster/new-cluster.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -355,6 +355,19 @@ An automated deployer command doesn't exist yet, these files need to be manually
355355
````
356356
`````
357357

358+
## Specify `hubspot_deal_id`
359+
360+
We want to match every cluster we deploy to a particular contract that we have to run it
361+
for a specific time. We manage contracts on Hubspot, and each contract is associated with
362+
a "Deal". We specify the id of this deal for each Cluster under `metadata.2i2c.hubspot_deal_id`,
363+
and it must be specified when creating the cluster. The new hub request issue should have
364+
a Hubspot deal URL, and you can determine the deal ID by either:
365+
366+
1. Opening the URL, logging into hubspot and looking in the sidebar
367+
2. Manually just look at the URL - if the URL of the deal looks like
368+
https://app-na2.hubspot.com/contacts/242496330/record/0-3/96602996427,
369+
the deal ID is the last integer, that comes after `0-3`.
370+
358371
## Add GPU nodegroup if needed
359372

360373
If this cluster is going to have GPUs, you should edit the generated jsonnet file

0 commit comments

Comments
 (0)