-
Notifications
You must be signed in to change notification settings - Fork 47
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
feature request: add support for other categories #67
Comments
I was expecting there to be something like "fields" that has an associative array of all the fields, and that some fields are aliased to those mentioned in the docs, for common categories like database. |
I was hoping to be able to create a note. As is, it seems like anything I create will have a |
@MarshallAsch - thanks for reaching out with this feature request and apologies for the delayed response. @krokofant and @iautom8things - thank you for your input as well. I can confirm that additional item types are on our radar, but I can't provide any commitments or timelines as of this writing. Thank you again for expressing your interest in this feature. |
Hey @dustin-ruetz any news on this? I can see the API supports different categories but still cannot use them with the terraform provider. Linking a correlated older issue: #52 |
Any update on this request? |
Are we going to see any updates to this? Would really like to have access to API Credentials and SSH Key as categories. |
Summary
1passoword supports more more types than just the
login
,password
, anddatabase
categories.Importing
server
items that were manually created into terraforms control will fail because they do that is not supported by this provider.Use cases
When people have manually created password items of a different category that they then wish to import.
Proposed solution
Add sport for the rest of the item types that can be stored in the vault.
Is there a workaround to accomplish this today?
There is no work around, perhaps manually recreating everything with the new type will work but thats not really a viable work around.
The text was updated successfully, but these errors were encountered: