Tracking encrypted blocks in edit mode about hiera-eyaml HOT 3 CLOSED

Its a good idea - my only comments would be:

1. it might be more readable to have the encoding type and the hash in memory, and just use counters - e.g. DEC(1):[content]! and DEC(2):[content]! - and the eyaml tool in memory has already stored the hash of the decrypted content of each block to comprare with post editing, and the encryption type?
2. alternatively you could use DEC::4b2a562f[ ]!

Both cases wouldnt allow the user to change the encryption type of a single block though

from hiera-eyaml.

That's an interesting idea that hadn't occured to me. You are right though, it wouldn't allow for the encryption mode to be changed and it might make it harder for users to create new encrypted values in an existing file.

I'm swaying towards DEC(#{index})::#{method}[#{content}]!

I started to look at this last night. It does mean completely rewriting the edit action and no longer reusing the decrypt and encrypt actions (I'd try and extract out the common elements).

from hiera-eyaml.

Closing this issue as this is now out of the door with 1.3.6

from hiera-eyaml.