archive_command is always 'exit 0' ?

[aaronireland]

There doesn't appear to be a way to set the archive_command. I need the master node to push WAL files to an AWS S3 bucket in order for streaming replication to work with my current (and preferred) setup. It seems like the default archive command for the postgresql.conf is injected as part of a big string in pgconfig.go. Am I missing something important here in the configuration? If not, is there a way to add the desired archive_command as part of the yoke.ini configuration?