* add shutdown function to TestVaultServer
* implement shutdown function in TestVaultServer
* stop renewing vault token when token has already expired
* Add comment
* clean up error checks
* modify credential_vault_token_renewal_revocation_view to include expiration_time
* include TokenExpirationTime in clientStore
* add test to validate that unexpired tokens are not set as expired
* add token status validation
* add expiration time validation to tests
* add small comment
* remove unnecessary renew from test
* fix token translation uses wrong time field and add tests
* add more token status validation
* fix lint
* move migration to 103
* remove t.Parallel() comments
* remove unused setup code
* use atomic for testvault.stopped
implement atomic read/write for testvault
* remove file created by merge conflict
* make gen
* internal/cmd/commands/server/listener_reload_test.go remove t.Parallel() comment
* internal/cmd/commands/server/worker_initial_upstreams_reload_test.go remove t.Parallel
* internal/cmd/commands/server/worker_tags_reload_test.go wait by polling worker instead of sleep
* internal/daemon/worker/routing_info.go make deep copy in LastRoutingInfoSuccess to avoid race condition
* internal/tests/cluster/parallel/orphaned_connections_test.go raise grace period time to allow test to wait for longer
* improve logging in sequential tests
* move ports around and use t.Cleanup to send shutdown signal to test server
* fix one typo
* do final assert in t.Cleanup instead of defer
* undo t.Cleanup change
* add another signal to force shutdown running servers
* add exit early and increase server start timeout
* tighten workerRPC settings on session tests
* tighten more workerRPC timing
* make gen
* add comment explaining deep copying lastRoutingInfoSuccess
* reactor: Update Password use of crypto/rand to SecureRandomReader
* changes updated
* make gen error changes
* make gen error changes
* new changes updated
* new changes updated
* Revert "new changes updated"
This reverts commit 85ee1d21867e26e7dac9ac28ba0e541a84345e90.
* Revert "new changes updated"
This reverts commit b4df84452397724465e00fc48169473148a26e3f.
* SecureRandomreader introduced to password
* SecureRandom pkg removed
* updated
With the refactor in version 99, the credential_vault_library_deleted
table was renamed to credential_vault_generic_library_deleted, but its
corresponding purge job was not removed from the job table, leading to
an error: "job credential_vault_library_deleted_items_table_purge not
registered on scheduler".
This commit deletes the legacy job entry. The new job that takes over
the legacy one is
credential_vault_generic_library_deleted_items_table_purge.
The existing credential_vault_library table is the table that holds operational
state for Vault generic credential libraries. This commit renames that table and
all its associated database entities to credential_vault_generic_library.
Additionally, a new credential_vault_library table is created as the base table
for all Vault-subtype credential libraries (eg: Vault generic, Vault SSH Cert).
* Update website folder to indicate deprecation
Adds an alert banner to the top of all MDX files within `/website` to
indicate deprecation
* Update website README
* moves resource-table.mdx to internal/website/permstable
* updates location of generated resource-table.mdx file to internal/website/permstable/
This change facilitates the implementation of the web-unified-docs content migration,
which will need to source generated content like this table from outside the website
folder after the content migration.
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>
* 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
Irena Rindos
Sorawis Nilparuk (Bo)
hashicc
Abhishek Manjegowda
Ryan Derr
Priya Patel
Hugo
dani
Louis Ruch
Justin Nguyen
Bharath Gajjala
Andrew Gaffney
Robert Main
Robin Beck
Johan Brandhorst-Satzkorn
April-May
David Kanney