You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Adrian Likins 042079aa87 Use vault_id when encrypted via vault-edit (#30772) ... * Use vault_id when encrypted via vault-edit On the encryption stage of 'ansible-vault edit --vault-id=someid@passfile somefile', the vault id was not being passed to encrypt() so the files were always saved with the default vault id in the 1.1 version format. When trying to edit that file a second time, also with a --vault-id, the file would be decrypted with the secret associated with the provided vault-id, but since the encrypted file had no vault id in the envelope there would be no match for 'default' secrets. (Only the --vault-id was included in the potential matches, so the vault id actually used to decrypt was not). If that list was empty, there would be an IndexError when trying to encrypted the changed file. This would result in the displayed error: ERROR! Unexpected Exception, this is probably a bug: list index out of range Fix is two parts: 1) use the vault id when encrypting from edit 2) when matching the secret to use for encrypting after edit, include the vault id that was used for decryption and not just the vault id (or lack of vault id) from the envelope. add unit tests for #30575 and intg tests for 'ansible-vault edit' Fixes #30575 (cherry picked from commit a14d0f3586)		7 years ago
..
compile	Docs how to test (2nd) (#24094)	8 years ago
integration	Use vault_id when encrypted via vault-edit (#30772)	7 years ago
results	Collect data from integration test runs. (#28650)	7 years ago
runner	Improve ansible-test HttpClient error handling. (#30301)	7 years ago
sanity	[fix] no-unicode-literals sanity error on ansible.egg-info (#30446)	7 years ago
units	Use vault_id when encrypted via vault-edit (#30772)	7 years ago
utils	Divide Windows integration tests into 2 groups. (#29029)	7 years ago