* chore(e2e): Update docker terraform provider to 3.6.2
* chore(e2e): Use boundary directory to avoid permission issues
* fix(e2e): Use tmpfs block to open up permissions of directory
* ce: chore(e2e): Address setup flakiness when getting hostname
* ce: refact(e2e): Enable token to be passed into methods
Co-authored-by: Michael Li <michael.li@hashicorp.com>
* refact(e2e): Add error output to SetupLdapWithOpenLdap
(cherry picked from commit 12874ec3227500ac03ece452e342f44d9f1ebc7a)
* test(e2e): Add method for setting up vault ldap with active directory
(cherry picked from commit 4f0fe7bba78d25005a5d98e203a3d0bc037a2b69)
* chore(e2e): Add domain controller ipv6 address to e2e tests
(cherry picked from commit 3215194053cd82a4e650522e56f4699946f62ef3)
* chore(e2e): Ensure go modules are downloaded for test user
* chore(e2e): Add additional debug lines in script
* chore(e2e): Exclude boundary-ui clone when zipping boundary src
* chore(e2e): Update vault version that has vault ldap feature
* chore(e2e): Fix firewall and security group rules
* chore(e2e): Setup ldaps
* CR: spacing
I think this was somehow accidentally included from Vault
back in the day and never removed. As far as I can tell
these options have absolutely no effect on anything
in Boundary and will probably only cause confusion.
* feat(mongo): add mongo for boundary cli
* Fix: remove changes added by mistake during testing
* feat(enos): install MongoDB client (mongosh) in e2e Docker test runtime
* Remove explicit Boundary DB/server startup from target_tcp_connect_mongo_test.go
* Add a full stop and trigger CI
* feat: add mongosh support to boundary connect mongo
* feat: add mongosh support to boundary connect mongo
* feat: add auth-source flag for MongoDB connect command
- Add -auth-source flag with default value 'admin' for root users
- Add BOUNDARY_CONNECT_MONGO_AUTH_SOURCE environment variable support
- Update documentation with new flag and correct mongosh default
- Improve MongoDB test with explicit auth-source parameter
- Fix Docker configuration formatting for better readability
This ensures MongoDB root users authenticate against the admin database
by default while allowing flexibility for custom authentication databases.
* test(e2e): Fixed false positive in Mongo connect test; use UriNetwork and container hostname
* make gen
* fix: Removed unnecessary variable containerName from the MongoDB E2E test
* feat(connect/mongo): Build URI compatible with mongosh and set default authSource
* feat(connect/mongo): use mongosh flags following PostgreSQL pattern
* remove 'connection string' from auth-source usage text
* Update internal/cmd/commands/connect/mongo.go
Co-authored-by: Bharath Gajjala <120367134+bgajjala8@users.noreply.github.com>
* remove 'connection string' from auth-source usage text
* refacotr: replace authSource flag with authenticationDatabase
---------
Co-authored-by: Enbiya <100806254+enbiyagoral@users.noreply.github.com>
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
* remove name var necessity in docker scenario
* rm log
* parse from docker load
* rm docker image name var from enos-variables
* rm boundary_docker_image_name from files
Rather than hard-coding a version and needing to update this every time it becomes deprecated, we just pick the current default that AWS has set (which should be close to the latest).
* add redis connect support
* Setup redis in docker for e2e testing
* Update docs and changelog
* Commenting out e2e tests for now, will revisit in a separate task
* chore(e2e): Add module for rdp member server
* CR: Update Domain mode to be compatible with newer versions of Windows
* CR: Add comments to ports
* CR: Simplify adding computer to the domain
The provider was returning the following warning, which will become an error in future versions of the provider.
No attribute specified when one (and only one) of [rule[0].filter,rules[0].prefix] is required
dillanb-hashi
Michael Li
Tony
Johan Brandhorst-Satzkorn
Pradeep Sekar
Justin Nguyen
Ryan DerrandBharath Gajjala