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

Documentation of vpc_attachments input parameter needed #125

Closed
zampettim opened this issue Jan 2, 2024 · 3 comments
Closed

Documentation of vpc_attachments input parameter needed #125

zampettim opened this issue Jan 2, 2024 · 3 comments

Comments

@zampettim
Copy link

Is your request related to a new offering from AWS?

Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

  • No 🛑: please wait to file a request until the functionality is avaialble in the AWS provider

Is your request related to a problem? Please describe.

The format and details about what is supposed to be supplied in the vpc_attachments input parameter is missing. The examples provide some details of what is expected, but looking at the code reveals that there are other parameters that could be supplied that would alter the behavior of the module. But even looking at the code can be a bit confusing and should not be required.

Describe the solution you'd like.

A full and detailed description of the format of the vpc_attachments input paramter should be documented, and updated examples that includes more use cases for both ipv4 and ipv6 and dual stack configurations would be ideal.

Describe alternatives you've considered.

None

Additional context

None

Copy link

github-actions bot commented Feb 2, 2024

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Feb 2, 2024
Copy link

This issue was automatically closed because of stale in 10 days

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 12, 2024
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 Mar 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant