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

Add Carrier Gateway support + Wavelength Zone subnet support for AWS Wavelength #893

Closed
rhbelson opened this issue Feb 7, 2023 · 7 comments
Labels

Comments

@rhbelson
Copy link

rhbelson commented Feb 7, 2023

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
  • Yes ✅: please list the AWS provider version which introduced this functionality

Is your request related to a problem? Please describe.

Describe the solution you'd like.

Describe alternatives you've considered.

Additional context

@github-actions
Copy link

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 Mar 10, 2023
@ForbiddenEra
Copy link

ForbiddenEra commented Mar 18, 2023

You can actually add wavelength zone subnets; however there IS a bug (see my annoyingly auto-closed "stale" issue at #864) that doesn't allow this to work if using IPv6/dualstack at all because WLZ doesn't do IPv6 and it breaks the module.

@github-actions github-actions bot removed the stale label Mar 19, 2023
@ForbiddenEra
Copy link

Bump before stale again, reminding that my issue #864 was closed, I can't re-open and I don't really want to create a new one for it and this is kinda related.

@ForbiddenEra
Copy link

I think #892 could be considered as a potential way forward for handling subnets; if not exactly how suggested there, at least improving the flexibility should be considered especially in cases like this where one wants to use WLZ and IPv6 together or otherwise.

@github-actions
Copy link

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 May 12, 2023
@github-actions
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 May 22, 2023
@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 Jun 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants