Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for compute cluster name for NSX Edge Node deployment #191

Closed
1 of 4 tasks
smctighevcp opened this issue Jun 20, 2024 · 1 comment · Fixed by #194
Closed
1 of 4 tasks

Allow for compute cluster name for NSX Edge Node deployment #191

smctighevcp opened this issue Jun 20, 2024 · 1 comment · Fixed by #194
Assignees
Labels
enhancement Enhancement

Comments

@smctighevcp
Copy link

Code of Conduct

  • I have read and agree to the project's Code of Conduct.
  • Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
  • Do not leave "+1" or other comments that do not add relevant information or questions.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Currently when deploying an NSX edge node the "compute_cluster_id" attribute is required. Currently this needs to be obtained manually via the API. Allowing for the cluster name would make deployment of and Edge node cluster easier, directly after deploying a VCF instance.

Use Case(s)

Allow for edge nodes clusters to be deployed as part of a wider VCF instance deployment without having to step outside of terraform to obtain the compute_cluster_id.

Potential Configuration

"compute_cluster_name": {
Type: schema.TypeString,
Required: true,
Description: "The name of the compute cluster",
ValidateFunc: validation.NoZeroValues,
},

References

No response

Copy link

I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants