Open ecsexec-tfaction[bot] opened 6 months ago
Apply complete! Resources: 2 added, 0 changed, 2 destroyed.
`
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
`
terraform plan
Error: Failed to get the data key required to decrypt the SOPS file.
Group 0: FAILED
02CD2DEFD3E49529DF7136DDB6B1A17F2B853ADB: FAILED
- | could not decrypt data key with PGP key:
| github.com/ProtonMail/go-crypto/openpgp error: could not
| load secring: open /home/runner/.gnupg/pubring.gpg: no such
| file or directory; GnuPG binary error: failed to decrypt
| sops data key with pgp: gpg: directory '/home/runner/.gnupg'
| created
| gpg: encrypted with ECDH key, ID 70409289B7C937B0
| gpg: decryption failed: No secret key
| gpg: [don't know]: invalid packet (ctb=63)
age14f3p6lva7tjjvlplqquacmnwu8m3zaz844cuel87nl2vdc6x65fsue5gtd: FAILED
- | failed to load age identities: failed to open file: open
| /home/runner/.config/sops/age/keys.txt: no such file or
| directory
Recovery failed because no master key was able to decrypt the file. In
order for SOPS to recover the file, at least one key has to be successful,
but none were.
with data.sops_file.secrets,
on github.tf line 9, in data "sops_file" "secrets":
9: data "sops_file" "secrets" {
Error: Failed to get the data key required to decrypt the SOPS file.
Group 0: FAILED
02CD2DEFD3E49529DF7136DDB6B1A17F2B853ADB: FAILED
- | could not decrypt data key with PGP key:
| github.com/ProtonMail/go-crypto/openpgp error: could not
| load secring: open /home/runner/.gnupg/pubring.gpg: no such
| file or directory; GnuPG binary error: failed to decrypt
| sops data key with pgp: gpg: keybox
| '/home/runner/.gnupg/pubring.kbx' created
| gpg: encrypted with ECDH key, ID 70409289B7C937B0
| gpg: decryption failed: No secret key
| gpg: [don't know]: invalid packet (ctb=5e)
age14f3p6lva7tjjvlplqquacmnwu8m3zaz844cuel87nl2vdc6x65fsue5gtd: FAILED
- | failed to load age identities: failed to open file: open
| /home/runner/.config/sops/age/keys.txt: no such file or
| directory
Recovery failed because no master key was able to decrypt the file. In
order for SOPS to recover the file, at least one key has to be successful,
but none were.
with data.sops_file.tf_secrets,
on main.tf line 43, in data "sops_file" "tf_secrets":
43: data "sops_file" "tf_secrets" {
terraform plan
Error: Failed to get the data key required to decrypt the SOPS file.
Group 0: FAILED
02CD2DEFD3E49529DF7136DDB6B1A17F2B853ADB: FAILED
- | could not decrypt data key with PGP key:
| github.com/ProtonMail/go-crypto/openpgp error: could not
| load secring: open /home/runner/.gnupg/pubring.gpg: no such
| file or directory; GnuPG binary error: failed to decrypt
| sops data key with pgp: gpg: directory '/home/runner/.gnupg'
| created
| gpg: keybox '/home/runner/.gnupg/pubring.kbx' created
| gpg: encrypted with ECDH key, ID 70409289B7C937B0
| gpg: decryption failed: No secret key
| gpg: [don't know]: invalid packet (ctb=63)
age14f3p6lva7tjjvlplqquacmnwu8m3zaz844cuel87nl2vdc6x65fsue5gtd: FAILED
- | failed to load age identities: failed to open file: open
| /home/runner/.config/sops/age/keys.txt: no such file or
| directory
Recovery failed because no master key was able to decrypt the file. In
order for SOPS to recover the file, at least one key has to be successful,
but none were.
with data.sops_file.secrets,
on github.tf line 9, in data "sops_file" "secrets":
9: data "sops_file" "secrets" {
Error: Failed to get the data key required to decrypt the SOPS file.
Group 0: FAILED
02CD2DEFD3E49529DF7136DDB6B1A17F2B853ADB: FAILED
- | could not decrypt data key with PGP key:
| github.com/ProtonMail/go-crypto/openpgp error: could not
| load secring: open /home/runner/.gnupg/pubring.gpg: no such
| file or directory; GnuPG binary error: failed to decrypt
| sops data key with pgp: gpg: Fatal: can't create directory
| '/home/runner/.gnupg': File exists
age14f3p6lva7tjjvlplqquacmnwu8m3zaz844cuel87nl2vdc6x65fsue5gtd: FAILED
- | failed to load age identities: failed to open file: open
| /home/runner/.config/sops/age/keys.txt: no such file or
| directory
Recovery failed because no master key was able to decrypt the file. In
order for SOPS to recover the file, at least one key has to be successful,
but none were.
with data.sops_file.tf_secrets,
on main.tf line 43, in data "sops_file" "tf_secrets":
43: data "sops_file" "tf_secrets" {
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
Apply complete! Resources: 0 added, 9 changed, 0 destroyed.
`
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.
This issus was created by tfaction.
About this issue, please see the document.