Add provider meta module_name in Equinix Metal TF configs

[codinja1188]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation4
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

Which issue(s) this PR fixes:

• It allows Vendor to declare the metadata fields. It adds provider meta module_name in Equinix Metal TF configs.
• To simplify user experience, we will replace the “facility” attribute in the Metal CLI and API with the “metro” attribute.

Related to equinix/terraform-provider-equinix#252

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Add provider meta module_name in Equinix Metal TF configs

Related to equinix/terraform-provider-equinix#252

[k8s-ci-robot]

Welcome @Vasubabu!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Vasubabu. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[displague]

/ok-to-test

[displague]

Suggested change

	# masters
	# masters

Spacing in these changes is offending the linter. It's hard to tell from the GitHub view, but it appears as though there are hundreds of spaces after the word masters. After addressing this, amend commit (keeping the PR as a single commit) and force push to avoid creating commit noise for this unintended change.

Please do the following to test this locally:

$ npm install -g markdownlint-cli@0.22.0
added 36 packages in 2s
2 packages are looking for funding
  run `npm fund` for details
$ markdownlint $(find . -name '*.md' | grep -vF './.git') --ignore docs/_sidebar.md --ignore contrib/dind/README.md
./docs/ci-setup.md:58:10 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 109]

[displague]

keeping the PR as a single commit

One or two separate commits. As two it would be one for the UA prefix and another for the facility to metro changes.

The PR description should mention why this is being done (facility deprecation):
https://feedback.equinixmetal.com/changelog/bye-facilities-hello-again-metros

[displague]

We'll want to update the two test variable references from facility to metro with the appropriate metro setting. (ewr1 -> ny, ams1 -> am, TF_VAR_facility -> TF_VAR_metro) in .gitlab-ci/terraform.yml

[displague]

It looks like CI has been fixed in recently merged PRs. Rebasing this PR should help to get the tests passing again.

[MrFreezeex]

Thanks for your contribution! :D
/lgtm

[displague]

/lgtm

[oomichi]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: oomichi, vasubabu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [oomichi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment