Change 29942
Customer Contributed changes:
1. I use a slightly different method to get the latest journal version (for appending to the snapshot name). The approach I had been using was running into some issues with the Perforce account not being logged into the Perforce server, so I borrowed the approach out of the existing SDP scripts to login and retrieve that value.
2. I've added a section at the end to automatically delete old snapshots when they age past a value that's configurable in the script. If snapshots were being generated automatically by AWS automation, this aging-off process would be part of that; since we're pushing the snapshot creation from the Perforce server, I needed to add this functionality, so I didn't have to go manually delete old versions from AWS occasionally.
1. I use a slightly different method to get the latest journal version (for appending to the snapshot name). The approach I had been using was running into some issues with the Perforce account not being logged into the Perforce server, so I borrowed the approach out of the existing SDP scripts to login and retrieve that value.
2. I've added a section at the end to automatically delete old snapshots when they age past a value that's configurable in the script. If snapshots were being generated automatically by AWS automation, this aging-off process would be part of that; since we're pushing the snapshot creation from the Perforce server, I needed to add this functionality, so I didn't have to go manually delete old versions from AWS occasionally.