Johan Brandhorst-Satzkorn 6238a533b0 internal/credential: sort public_id descending ...

The previous sort would run the risk of missing items which
collide on update or create times because of the compound
comparison using strictly less than for both the timestamp
and the public_id. Sorting both descending avoids thi issue.

2024-01-05 07:43:21 -08:00

..

static

internal/credential: sort public_id descending

2024-01-05 07:43:21 -08:00

store

…

vault

internal/credential: sort public_id descending

2024-01-05 07:43:21 -08:00

credential.go

…

options_test.go

…

options.go

…

public_ids.go

…

query.go

internal/credential: sort public_id descending

2024-01-05 07:43:21 -08:00

redact_test.go

…

redact.go

…

registry.go

…

repository_store_test.go

…

repository_store.go

…

service_list_credentials_ext_test.go

…

service_list_credentials_page.go

…

service_list_credentials_refresh_page.go

…

service_list_credentials_refresh.go

…

service_list_credentials.go

…

service_list_libraries_ext_test.go

…

service_list_libraries_page.go

…

service_list_libraries_refresh_page.go

…

service_list_libraries_refresh.go

…

service_list_libraries.go

…

service_list_stores_ext_test.go

…

service_list_stores_page.go

…

service_list_stores_refresh_page.go

…

service_list_stores_refresh.go

…

service_list_stores.go

…

store.go

…