DOCSP-45053 added tags to hierarchy create cluster page

[kyuan-mongodb]

For Terraform, I used this page as a reference.

JIRA
Staging

[netlify]

✅ Deploy Preview for docs-atlas-architecture ready!

Name	Link
🔨 Latest commit	31a27cb
🔍 Latest deploy log	https://app.netlify.com/sites/docs-atlas-architecture/deploys/672e3c6411b6920008126805
😎 Deploy Preview	https://deploy-preview-32--docs-atlas-architecture.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sarahsimpers]

Hi Kailie, I just tried to test this for the CLI and it didn't work, please see the attached error. Also, we're missing examples for Dev and Test environments. Please add those examples as well (may require changing format for the CLI dev/test to use a cluster config file), and test before resubmitting. Thanks!

[sarahsimpers]

Add dev/test examples, test to ensure all work

[mmarcon]

@kyuan-mongodb what is the reason for using the CLI command with parameters for dev and test environments and with JSON file for staging and production?

[kyuan-mongodb]

Hi @mmarcon, We're adding in tags because we suggest users to do so higher on the page here.

[lantoli]

the link in the PR description is incorrect because it's for cluster (which will be deprecated), the correct documentation for advanced_cluster is: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/advanced_cluster

so tags should be defined as:

tags {
  key   = "BU"
  value = "ConsumerProducts"
}
tags {
  key   = "TeamName"
  value = "TeamA"
}

etc.

same for example below

[mmarcon]

@kyuan-mongodb apologies if my questions was not clear. What I mean is why do we use command line parameters in one case (dev and test) but we use the --file option with a JSON file in the other case (stg and prod)? Why not picking one way and using that for both?

[sarahsimpers]

@kyuan-mongodb apologies if my questions was not clear. What I mean is why do we use command line parameters in one case (dev and test) but we use the --file option with a JSON file in the other case (stg and prod)? Why not picking one way and using that for both?

Hi @mmarcon, we did this both because the dev example was simple enough to do this (while the prod example will eventually be too complex to do without a config file), and to showcase different ways to accomplish this.

[mmarcon]

Thank you @sarahsimpers - ok. I am usually in support of consistency, but I also see the value of showing that there are multiple ways to achieve the same thing. I don't know if we want to add an extra note about that so we don't create confusion.
Or alternatively we could use a language selector and allow the user to switch to one or the other representation. That'd be cool actually.

I'll LGTM to not keep you blocked given that I am traveling and slow to respond, but if we have an easy enough way to avoid confusion please consider it. TY!