ischluff / terraform-provider-keepass Goto Github PK

Description:

I encountered an error while running terraform init with the ischluff/keepass provider v1.0.0. The error message indicates that the installation failed due to an expired OpenPGP key.

╷
│ Error: Failed to install provider
│
│ Error while installing ischluff/keepass v1.0.0: error checking signature:
│ openpgp: key expired
╵

Steps to Reproduce:

1. Run terraform init with the following configuration

provider "keepass" {
  database = "***"
  password = ***
}

Terraform Version: v1.6.0
Operating System: Linux
Provider Version: ischluff/keepass v1.0.0

Could you please update the OpenPGP key or provide guidance on how to resolve this issue?

Would you consider adding a license (eg. Apache 2.0) so the legal status is clear to people using this component?

Unless license is mentioned somewhere already and I didn't notice?

Hi I keep getting the error: Error: group Root in path Root/test/test not found, although the correct database structure is there. One thing to note, I created my database in Windows 10 and now I am trying to run terraform on it using a remote linux server. Is there any way to see which path list that the keepass provider understands?

I am using the example in the terraform/github docs

data "keepass_entry" "test" {
  path = "Root/test/test"
}

Any idea what the issue could be?

I need to add resources in the keepass database via terraform.

To do this I created a resource "keepass_entry" that allows addition of keepass entries to this provider. Allowing VMs to be provisioned by cloud-init, generating a ssh-key inside terraform and finally exporting the ssh-keys to keepass, where you can use keepassXC's feature to connect to your local ssh-agent to seamlessly use those keys for the provisioned machines.

The change is a quite large commit in a fork of your repository:

Eusebius1920@2f4bbc0

I wanted to hear your opinion if you would be willing to accept this as a contribution to your provider? It is quite a big change to the existing code-base. If so, I would then create a Pull-Request to get that going.

The following things would need to be adjusted by me ( - I am currently using it only for myself, so I skipped these parts):

• polish a few rough edges (review sensitive flags, unify logging, ...)
• missing tests for the new code
• update docs
• somehow test if the implementation is really still platform independent. I used fsnotify which claims to be platform independent, but I still have only tested it on linux?

I would like to hear your thoughts about this!