Update rclone provisioning play to generate config with AWS credential files for users

User story

As a curator I want the tools on bastion to allow me to perform files operations on Wasabi with rclone So that I can manage the dataset files on Wasabi

Acceptance criteria

Given a bastion server is provisioned for the first time When I run the playbook play that install rclone Then rclone is installed on the bastion server And an rclone configuration file referencing default AWS credential file location is created for centos user

Given a new bastion user has been added to the bastion When I run the playbook play that install rclone Then rclone is updated on the bastion server And an rclone configuration file referencing default AWS credential file location is created for the new bastion user

Additional Info

See: https://rclone.org/s3/#authentication

this ticket is not for creating the actual user's AWS Credential file. That's why it depends on:

[x] #1394

Implementation notes

* [ ] Create a template ops/configuration/aws/credentials.j2 using existing variables wasabi_access_key_id and wasabi_secret_access_key * [ ] Update template ops/configuration/rclone-conf/rclone.conf.j2, to remove keys from the [wasabi] profile * [ ] Add task to generate aws credentials from template in bastion playbook * [ ] Add task in bastion playbook to run rclone ls to verify that configuration works

[x] #1834

Product Backlog Item Ready Checklist

[ ] Business value is clearly articulated
[ ] Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
[ ] Dependencies are identified and no external dependencies would block this item from being completed
[ ] At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
[ ] This item is estimated and small enough to comfortably be completed in one sprint
[ ] Acceptance criteria are clear and testable
[ ] Performance criteria, if any, are defined and testable
[ ] The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

[ ] Item(s) in increment pass all Acceptance Criteria
[ ] Code is refactored to best practices and coding standards
[ ] Documentation is updated as needed
[ ] Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
[ ] No deviation from the team technology stack and software architecture has been introduced
[ ] The product is in a releasable state (i.e. the increment has not broken anything)

gigascience / gigadb-website