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

feat: Adding support for fetching avalible ip from multiple subnets. #580

Open
wants to merge 30 commits into
base: master
Choose a base branch
from

Conversation

sanderskjulsvik
Copy link

@sanderskjulsvik sanderskjulsvik commented May 2, 2024

Feature: add support for multiple subnets for available_ip_address.
This will allow the resource available_ip_address to get an ip address from a collection of ip_ranges or subnets.

This solves the problem where we have run out of IP addresses in a subnet, and now need to create more with the same IAC setup

@fbreckle
Copy link
Collaborator

fbreckle commented May 3, 2024

Is this something that can be built into the existing available_ip resource?

@sanderskjulsvik
Copy link
Author

sanderskjulsvik commented May 3, 2024 via email

@sanderskjulsvik
Copy link
Author

Did not get ranges to work. Got nil in payload. So I will remove the support for multiple ranges

@sanderskjulsvik
Copy link
Author

Nvm, The nil payload was because of typo

@sanderskjulsvik
Copy link
Author

make testacc now works on my pc @dd4253858c21c847890a202a0302cbcea255e89a.

@sanderskjulsvik sanderskjulsvik changed the title Adding support for fetching avalible ip from multiple subnets. feat: Adding support for fetching avalible ip from multiple subnets. May 8, 2024
@sanderskjulsvik sanderskjulsvik marked this pull request as ready for review May 13, 2024 18:16
@sanderskjulsvik
Copy link
Author

Seems like my tests are now failing.

@sanderskjulsvik
Copy link
Author

@fbreckle or someone else, this is ready for a review. Please let me know of you have any comments on this feature.

@fbreckle
Copy link
Collaborator

The errors in your test regarding custom fields are just a race condition we currently have. My guess is that it happens during parallel tests when one test introduces a custom field while your own test runs, causing the api to return an unexpected custom field in your test.
I re-ran the tests and theyre now green. Will review this this week.

@fbreckle
Copy link
Collaborator

Can you allow me to push to your repo? I have some changes and just found that i cannot push there.
You can set a checkbox in your PR to allow me push access to your fork. See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork step 7

@sanderskjulsvik
Copy link
Author

Hi, sorry for my delayed answer, I had a temporary distraction. We cannot give you write access to this repo, could you open a pr to my repo?

@sanderskjulsvik
Copy link
Author

Hi, have you had a chance to take a look at my changes?

@sanderskjulsvik
Copy link
Author

Can you allow me to push to your repo? I have some changes and just found that i cannot push there. You can set a checkbox in your PR to allow me push access to your fork. See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork step 7

Hi, is this is a blocker on your side to get this pr merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants