* 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
* feat: add MySQL command support
* Fix MySQL connection according to review feedback
* Update internal/cmd/commands/connect/mysql.go
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
* Update internal/cmd/commands/connect/mysql.go
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
* Update internal/cmd/commands/connect/mysql.go
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
* feat: add MySQL support to boundary connect
* docs: add MySQL to navigation menu
Fixes content check error by adding mysql.mdx to docs navigation.
MySQL page now appears in Commands > connect section alongside postgres.
* Update testing/internal/e2e/tests/base_plus/target_tcp_connect_mysql_test.go
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
* test: add containerized MySQL connection test for target functionality
* Remove MySQL environment variables from e2e test config
* test: move MySQL e2e test from base_plus to base folder
* Fix MySQL test to support both MySQL and MariaDB clients
* Fix MySQL test to support both MySQL and MariaDB clients
* lint cleanup
* adding error checks
* Make gen
* Test case testing
* Reverting bad comment
* cleaning up extra test file
* Add Mysql to runner (#5893)
* Adding back correct test file
* Removing base plus test file
* Removing base plus test file
* Revert "Removing base plus test file"
This reverts commit ace9cb3e90a028adc1f7c8ef55436ca843abfc15.
* forcing enos docker network name
* Revert "forcing enos docker network name"
This reverts commit 631bdb4a0ef87f5435e06456e8ec0a4573ab3e49.
* changing hosts to looks for sql container
* fix container name
* Adjusting for e2e tests and a bit of cleanup
* missed a commented string
* Bgajjala mysql e2etest v2 (#5900)
* Using Env Vars rather than parsing uri
* Comments fix
* spacing
* Update testing/internal/e2e/tests/base/target_tcp_connect_mysql_test.go
* Spacing
* Update internal/cmd/commands/connect/mysql.go
* adding error checks
* Make gen
* Update testing/internal/e2e/tests/base/target_tcp_connect_mysql_test.go
* Update internal/cmd/commands/connect/mysql.go
* Make gen
* derving target port from uri
* nit
* updating test to use url strings
* nit: spacing
* nit: code organization
* nit: code organization
Co-authored-by: Enbiya Göral
---------
Co-authored-by: Enbiya <menbiyagoral@gmail.com>
Co-authored-by: Enbiya Göral <100806254+enbiyagoral@users.noreply.github.com>
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
Co-authored-by: Ryan Derr <54389874+RyanDerr@users.noreply.github.com>
On destroy, there was an issue with deleting IAM roles due to the following error: DeleteConflict: Cannot delete entity, must detach all policies first
This commit adds an option to force the policy detachment, preventing the error.
dillanb-hashi
Michael Li
Johan Brandhorst-Satzkorn
Pradeep Sekar
Tony
Justin Nguyen
Ryan DerrandBharath Gajjala
hashicc
Hugo
