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

Typo in argument reference for aws_fsx_ontap_storage_virtual_machine resource #22238

Closed
khan-belal opened this issue Dec 15, 2021 · 2 comments
Closed
Labels
bug Addresses a defect in current functionality. service/fsx Issues and PRs that pertain to the fsx service.

Comments

@khan-belal
Copy link

khan-belal commented Dec 15, 2021

When attempting to add the argument "organizational_unit_distinguished_name" under the aws_fsx_ontap_storage_virtual_machine resource

terraform returns the following error:

An argument named "organizational_unit_distinguished_name" is not expected here. Did you mean │ "organizational_unit_distinguidshed_name"?

Using the suggested name (organizational_unit_distinguidshed_name) works when pushing the changes to AWS. This is a typo as this argument is referenced as organizational_unit_distinguished_name in the terraform documentation https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/fsx_ontap_storage_virtual_machine#organizational_unit_distinguished_name

Can this be corrected?

@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Dec 15, 2021
@ewbankkit ewbankkit added bug Addresses a defect in current functionality. service/fsx Issues and PRs that pertain to the fsx service. and removed needs-triage Waiting for first response or review from a maintainer. labels Dec 15, 2021
@ewbankkit
Copy link
Contributor

@k1ngkhan Thanks for raising this issue.
It has already been noticed in #21987. I'm going to close this one as a duplicate so that we can concentrate discussion in the linked issue.
Please add any additional comments there.

@github-actions
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 May 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/fsx Issues and PRs that pertain to the fsx service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants