v0.5.0

• No changes

v0.4.1

🐛 Bug Fixes

Can run this module under Alpine / Busybox @sodre (#3)

Describe the Bug

base64 --wrap=0 does not exist on alpine.

Expected Behavior

That the module would work.

Steps to Reproduce

Run example/complete under alpine box

Screenshots

resource "null_resource" "contents_if_missing" {
      - id       = "6203836822046158938" -> null
      - triggers = {
          - "exitstatus" = "0"
          - "stderr"     = <<~EOT
                base64: unrecognized option: wrap=0
                BusyBox v1.31.1 () multi-call binary.
                
                Usage: base64 [-d] [FILE]
                
                Base64 encode or decode FILE to standard output
                	-d	Decode data
            EOT
          - "stdout"     = ""
        } -> null
    }

Environment (please complete the following information):

Anything that will help us triage the bug will help. Here are some ideas:

• OS: Alpine + BusyBox
• Version [e.g. 10.15]

Additional Context

Add any other context about the problem here.

v0.4.0

Add SMIME encryption support @sodre (#2)

what

Add ability to encrypt content_base64 using SMIME.

why

RSA public key encryption only supports encrypting content that is smaller than the key size, e.g. a 2048-bit RSA key can only encrypt up to about 245 bytes using v1.5 padding.
SMIME does not have this limitation.

references

• https://www.xspdf.com/resolution/53205056.html

v0.3.0

Remove typo in examples/complete @sodre (#1)

what

• Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
• Use bullet points to be concise and to the point.

why

• Provide the justifications for the changes (e.g. business case).
• Describe why these changes were made (e.g. why do these commits fix the problem?)
• Use bullet points to be concise and to the point.

references

• Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
• Use closes #123, if this PR closes a GitHub issue #123

v0.2.0

• No changes

Initial Release

🚀 Initial release