Update Active Directory Query V2 to use LDAP docker image #29069
Conversation
…ync-issues-servicenow-v2
…ync-issues-servicenow-v2
…ctive-directory-invalid-address
…ctive-directory-invalid-address
…ctive-directory-invalid-address
…ctive-directory-invalid-address
…com/demisto/content into ay-active-directory-invalid-address
| @@ -2543,29 +2543,34 @@ | |||
| "playbookID": "Active Directory Test", | |||
| "integrations": "Active Directory Query v2", | |||
| "instance_names": "active_directory_ninja", | |||
| "memory_threshold": 100, | |||
There was a problem hiding this comment.
@anas-yousef - please explain those changes.
There was a problem hiding this comment.
The build was failing, as can be seen here (line 2562), due to insufficient memory.
…ctive-directory-invalid-address
…com/demisto/content into ay-active-directory-invalid-address
|
Need a force merge due to known NG issues. |
|
This PR requires a force merge because: |
) * Created test instance to send to user * Integration now uses LDAP docker image, which is debian based * Removed wrong files * Added RNs * Added memory_threshold=100 * Added memory_threshold * Fixed conflicts * Added memory threshold again after conflicts * Update Active_Directory_Query.yml * Update 1_6_22.md --------- Co-authored-by: Jasmine Beilin <71636766+JasBeilin@users.noreply.github.com>
Status
Related Issues
fixes: https://jira-hq.paloaltonetworks.local/browse/XSUP-24646
Description
Changed the docker image of the Active Directory Query V2 integration to the LDAP docker image, which now uses a debian based docker image.
Must have