-
Notifications
You must be signed in to change notification settings - Fork 88
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
Next available IP for recordAAAA, recordHost #244
Merged
JkhatriInfobox
merged 10 commits into
infobloxopen:dev_v2.8.0
from
Aish-sp:next-available
Oct 3, 2024
Merged
Next available IP for recordAAAA, recordHost #244
JkhatriInfobox
merged 10 commits into
infobloxopen:dev_v2.8.0
from
Aish-sp:next-available
Oct 3, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r ZoneForward and ZoneDelegated objects.
JkhatriInfobox
approved these changes
Oct 3, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Support for Next Available functionality, accepting partial changes to move forward with dev branch
JkhatriInfobox
added a commit
that referenced
this pull request
Oct 29, 2024
* Added support for ZoneDelegated object (#242) * go-client changes for zone-delegated object to support other fields * adding unit and e2e testcases for zone-delegated object * upgrading ginkgo, gomega version and corresponding change in suite_test file * updating vendor folder for ginkgo and gomega libraries version upgrade * changing the struct name from NullForwardTo to NullableNameServers for ZoneForward and ZoneDelegated objects. * updating vendor directory for ginkgo and gomega libraries upgrade. * Fix for NPA-165 (#243) * Next available IP for recordAAAA, recordHost (#244) * go-client changes for zone-delegated object to support other fields * adding unit and e2e testcases for zone-delegated object * upgrading ginkgo, gomega version and corresponding change in suite_test file * updating vendor folder for ginkgo and gomega libraries version upgrade * changing the struct name from NullForwardTo to NullableNameServers for ZoneForward and ZoneDelegated objects. * updating vendor directory for ginkgo and gomega libraries upgrade. * Support for next_available_network for NW and NW conatiner creation * adding next-available-ip support for RecordA and RecordAAAA objects * adding next_available_IP support for recordAAAA and recordHost --------- Co-authored-by: Jeenitkumar Khatri <58591067+JkhatriInfobox@users.noreply.github.com> * adding support for next-available-ip for host record and unit testcases for NW, NWC next-available-network. (#247) * [ADD] Testcases for A and AAAA with next-available function (#248) * Feature/next available (#249) * adding support for next-available-ip for host record and unit testcases for NW, NWC next-available-network. * adding e2e TCs for NW, NWC, RecordA, AAAA, HostRecord and unit testcases for hostRecord * Adding support for other fields for next-available-ip for host record --------- Co-authored-by: Jeenitkumar Khatri <58591067+JkhatriInfobox@users.noreply.github.com> * bugfix for next-available (#250) * bugfix for next-available * fix for:NPA-198: unable to set enable_dns field in hostRecord * updating unit and e2e testcases for a, aaaa and host records * NPA-200-fix: removing omitempty tag for aliases field of hostrecord (#252) * NPA-204 Fix - adding dbs_view for A ans AAAA records. (#253) * NPA-200-fix: removing omitempty tag for aliases field of hostrecord * NPA-204- FIX: adding dns view for A and AAAA records. * testcases for alias field in host record (#251) * adding negative scenarios to next-available testcases (#254) * E2E testcases-goclient (#256) * remove disable field in object_generated and added it to SearchHostRecordByAltId (#257) --------- Co-authored-by: Aish-sp <163982471+Aish-sp@users.noreply.github.com> Co-authored-by: Chaithra <chaithra@infoblox.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.