sops/functional-tests/.sops.yaml

creation_rules:
    - path_regex: test_roundtrip_keygroups.yaml
      key_groups:
      - pgp:
        - 1022470DE3F0BC54BC6AB62DE05550BC07FB1A0A
      - pgp:
        - 729D26A79482B5A20DEAD0A76945978B930DD7A2
    - path_regex: test_roundtrip_keygroups_missing_decryption_key.yaml
      key_groups:
      - pgp:
        - 1022470DE3F0BC54BC6AB62DE05550BC07FB1A0A
      - pgp:
        - 620B9A4C96230B91E7473D20113D2B26EA0890C7
    - pgp: 1022470DE3F0BC54BC6AB62DE05550BC07FB1A0A
destination_rules:
    - s3_bucket: "sops-publish-functional-tests"
      s3_prefix: "functional-test/"
      path_regex: test_encrypt_publish_s3.json
      reencryption_rule:
        pgp: 620B9A4C96230B91E7473D20113D2B26EA0890C7
Test file encryption 2016-11-13 18:36:43 +03:00			`creation_rules:`
Implement `sops publish` command (#473) * Implement `sops publish` command Publishes a file to a pre-configured destination (this lives in the sops config file). Additionally, support re-encryption rules that work just like the creation rules. Initial support for S3/GCS. This is a part of the sops-workspace v2.0 project Includes the addition of a new dependency: github.com/googleapis/gax-go/v2 * code review changes; support global --verbose flag * Switch to recreation_rule with full support Reencryption rule is now recreation rule and supports everything that a creation rule does. Now, when you load a config for a file, you load either the creation rule or the destination rule. I'm not sure about this style long term, but it allows for support to be added for the recreation rules without a bigger refactor of how the config file works. * split loadForFileFromBytes into two functions remove branching based on destination rule or not, create one for creation rules and one for destination rules * pretty diff for keygroup updates in sops publish 2019-06-27 19:48:54 +03:00			`- path_regex: test_roundtrip_keygroups.yaml`
Fix shamir tests 2017-08-25 23:12:34 +03:00			`key_groups:`
Allow using lists in key groups in .sops.yaml 2017-09-12 21:38:03 +03:00			`- pgp:`
			`- 1022470DE3F0BC54BC6AB62DE05550BC07FB1A0A`
			`- pgp:`
			`- 729D26A79482B5A20DEAD0A76945978B930DD7A2`
Implement `sops publish` command (#473) * Implement `sops publish` command Publishes a file to a pre-configured destination (this lives in the sops config file). Additionally, support re-encryption rules that work just like the creation rules. Initial support for S3/GCS. This is a part of the sops-workspace v2.0 project Includes the addition of a new dependency: github.com/googleapis/gax-go/v2 * code review changes; support global --verbose flag * Switch to recreation_rule with full support Reencryption rule is now recreation rule and supports everything that a creation rule does. Now, when you load a config for a file, you load either the creation rule or the destination rule. I'm not sure about this style long term, but it allows for support to be added for the recreation rules without a bigger refactor of how the config file works. * split loadForFileFromBytes into two functions remove branching based on destination rule or not, create one for creation rules and one for destination rules * pretty diff for keygroup updates in sops publish 2019-06-27 19:48:54 +03:00			`- path_regex: test_roundtrip_keygroups_missing_decryption_key.yaml`
Fix shamir tests 2017-08-25 23:12:34 +03:00			`key_groups:`
Allow using lists in key groups in .sops.yaml 2017-09-12 21:38:03 +03:00			`- pgp:`
			`- 1022470DE3F0BC54BC6AB62DE05550BC07FB1A0A`
			`- pgp:`
			`- 620B9A4C96230B91E7473D20113D2B26EA0890C7`
Test file encryption 2016-11-13 18:36:43 +03:00			`- pgp: 1022470DE3F0BC54BC6AB62DE05550BC07FB1A0A`
Implement `sops publish` command (#473) * Implement `sops publish` command Publishes a file to a pre-configured destination (this lives in the sops config file). Additionally, support re-encryption rules that work just like the creation rules. Initial support for S3/GCS. This is a part of the sops-workspace v2.0 project Includes the addition of a new dependency: github.com/googleapis/gax-go/v2 * code review changes; support global --verbose flag * Switch to recreation_rule with full support Reencryption rule is now recreation rule and supports everything that a creation rule does. Now, when you load a config for a file, you load either the creation rule or the destination rule. I'm not sure about this style long term, but it allows for support to be added for the recreation rules without a bigger refactor of how the config file works. * split loadForFileFromBytes into two functions remove branching based on destination rule or not, create one for creation rules and one for destination rules * pretty diff for keygroup updates in sops publish 2019-06-27 19:48:54 +03:00			`destination_rules:`
			`- s3_bucket: "sops-publish-functional-tests"`
			`s3_prefix: "functional-test/"`
			`path_regex: test_encrypt_publish_s3.json`
			`reencryption_rule:`
			`pgp: 620B9A4C96230B91E7473D20113D2B26EA0890C7`