what's the frequency of the letter "i" in:
post https://myhostnameisinhere/v1/vaults/vaultidishere/items: 400 - validation: (validatevaultitem failed to validate), couldn't validate the item: "[itemvalidator] has found 1 errors, 0 warnings: \nerrors:{1. required field \"item.templateuuid\" not found}"
this would seem to indicate that a templateuuid parameter is required; however, what is this? it is not mentioned in the api documentation, and even adding it to the passed attributes structure doesn't help.
value: "created by api"
we do not currently have any officially supported ruby sdk for connect. however, the error you are receiving looks to be indicating that you are not supplying a category (the templateuuid refers to the item category) for your 1password item, however from your example it appears you are supplying this, which is odd.
can you perhaps share with us which third party repo you are using so we can further look into this?
@jillian_1p - thanks for taking a look.
the ruby sdk is just a wrapper for the api, and i pass it the same json block (see above).
i pass a category parameter, same as in the documentation, but not a templateuuid parameter - i take it that this is the same thing?
it's not clear, but am i passing the fields array correctly? i am not sure if you need id/type/purpose/value/label to all be set, particularly for username, password and notes. also there is inconsistency in that the item object example in the doc shows these fields with id/type/label defined but the field object definition in the doc seems in indicate that type is not required if you have purpose, and id and label are not mentioned at all.
we've tested your json by submitting it directly to connect via an api request and the item was created successfully on our end. we dug a little deeper and tested the ruby sdk and were able to to replicate your issue. it looks as if the ruby sdk is sending connect an empty request body on post. your issue has shown us that we need better validation messages in this instance, so we will make an internal issue to work on this.
where we don't own this repo, this will need to be resolved by the owner of the ruby sdk, though i see you've already made an issue there.
lastly, when creating a field only the id and type are required.
many thanks for the help. hopefully the sdk maintainer will fix this fairly large problem soon.
problem solved! details here for the benefit of anyone else in the future.
calling the function like this and it all works. other calls also require parameters to be given in this way rather than as a single hash.
the update_item() function is broken however (sdk 0.1.3) and needs a fix in the library, see issues in the git repo.
as a suggestion, you can raise the documentation problem as a separate issue and provide the example that works. or even better, maybe they can enhance the function to support the signature they give as an example.
as for making connect sdks for other programming languages, we are aware that we can further expand the number of integrations available for connect: from sdks, to infrastructure integrations and ci/cd pipelines. we want folks to be able to easily adopt connect in their environment.
user
I found 191 "i"s in the provided passage.
assistant