Open g0dfl3sh opened 16 hours ago
I'm assuming you substitute PATH_TO_UID
with actual record UID
(no path included - since UIDs are unique)
If you have v2 records inside a folder shared to KSM App those records are invisible to KSM and General
record type and corresponding data sources/resources will be removed in the next release v1.1.5 (KSM-562 Removed data source type general)
General
is the legacy format, used for records created before the launch of Record Types and KSM works only with the new typed records but you can convert your legacy/v2 records to typed/v3 records (using Keeper Commander or web vault in your browser). Both newly created records/v3 and "General/v2" record versions can be converted between types.
Code for reproducing the error
Output
Expected Output
Plan should run without errors given the fact that the record with the given UID exists.
I believe the provider documentation in lacking in this regard. Keeper documentation mentions that general is a
Legacy format, used for records created before the launch of Record Types.
and mentionsThe record is a legacy (V2) non-typed record
as a reason for getting therecord not found
error.I am open to submitting a PR in order to fix the docs if you decide that's the right thing to do.