Describe the bug
After upgrading to v1.9.0, the LZA config is being written to the metadata log archive bucket as a byte array rather than YAML. Please see this line which was introduced in v1.9.0 which may be the culprit.
To Reproduce
Upgrade to v1.9.0 and validate that the format of the config files stored in the Log Archive's metadata bucket are now in byte array. Example:
104,111,109,101,82,101,103,105,111,110,58,32,38,72,79,77,69,95,82,69,71,73,79,78,32,99,97,45,99,101,110,116,114,97,108
Expected behavior
The format of the config files stored in the Log Archive's metadata bucket should be in YAML.
Example:
homeRegion: &HOME_REGION ca-central-1
centralSecurityServices:
delegatedAdminAccount: Audit
ebsDefaultVolumeEncryption:
[etc...]
Please complete the following information about the solution:
joeldesaulniers
commented
4 weeks ago
Describe the bug After upgrading to v1.9.0, the LZA config is being written to the metadata log archive bucket as a byte array rather than YAML. Please see this line which was introduced in v1.9.0 which may be the culprit.
To Reproduce Upgrade to v1.9.0 and validate that the format of the config files stored in the Log Archive's metadata bucket are now in byte array. Example: 104,111,109,101,82,101,103,105,111,110,58,32,38,72,79,77,69,95,82,69,71,73,79,78,32,99,97,45,99,101,110,116,114,97,108
Expected behavior The format of the config files stored in the Log Archive's metadata bucket should be in YAML. Example: homeRegion: &HOME_REGION ca-central-1 centralSecurityServices: delegatedAdminAccount: Audit ebsDefaultVolumeEncryption: [etc...]
Please complete the following information about the solution: