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

bugfix for next-available #250

Merged
merged 3 commits into from
Oct 22, 2024

Conversation

Aish-sp
Copy link
Collaborator

@Aish-sp Aish-sp commented Oct 21, 2024

Added support for disable for Host record

Copy link
Collaborator

@JkhatriInfobox JkhatriInfobox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes looks good to me

@JkhatriInfobox JkhatriInfobox merged commit 4114f9a into infobloxopen:dev_v2.8.0 Oct 22, 2024
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants