Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No way to persist an entry's $entry.KPEntry.Strings to database since the breaking changes in Cmdlet naming #201

Open
oleschri opened this issue Nov 19, 2021 · 0 comments

Comments

@oleschri
Copy link

oleschri commented Nov 19, 2021

With the old Cmdlets Set-KP... I was able to modify an entry including custom values via $kpentry.Strings and persist them to the database. I cannot find a way to do that with the 'new' *-KeePass* Cmdlets.

Update-KeePassEntry only takes the uuid from the passed entry object and updates the values specified in parameters but ignores everything else inside the passed entry object. :(

Old way that worked:

            $entry.Strings.Set('Custom Value 1', (Get-KeePassProtectedString 'ABC'))
            $entry.Strings.Set('Custom Value 2', (Get-KeePassProtectedString '123'))
            $conn.Save($null)
            $conn.Close()

Shouldn't there be an additional variant of Update-KeePassEntry that only takes the databaseprofile etc and a given entry in memory that persist all properties of that entry to the database?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant