Log into the ec2 instance through the following commands
$ awsmfa prod ######
Generating new IAM STS Token ...
STS Session Token generated and saved in profile mfa successfully.
$ microservice_ssm
$ cd /home/microservice/branch/GDXDSD-7112_looker_dashboard_usage_sqlalchemy/looker_dashboard_usage
Testing the looker_dashboard_usage.py script
Run the following command to test the looker_dashboard_usage microservice and compare its output to what's expected.
$ /home/microservice/.local/bin/pipenv run python3.8 looker_dashboard_usage.py looker_dashboard_usage.json
This PR does the following:
Testing the changes in this microservice requires a file to be modified. This test file will be attached to the ticket
File review:
Logging into the EC2 testing environment:
Testing the looker_dashboard_usage.py script
Config: looker_dashboard_usage.json
This microservice ran: successful
Microservice started at: 2024-08-26 16:55:56-0700 (PDT), ended at: 2024-08-26 16:55:57-0700 (PDT), elapsing: 0:00:01.535820.
Objects to process: 4 Objects that failed to process: 0 Objects output to 'processed/good': 4 Objects output to 'processed/bad': 0
List of objects successfully fully ingested from S3, processed, loaded to S3 ('good'), and copied to Redshift:
client/doug_test/GDXDSD-7112/looker_dashboards/dashboard.2024-08-25
client/doug_test/GDXDSD-7112/looker_dashboards/history.2024-08-25
client/doug_test/GDXDSD-7112/looker_dashboards/user.2024-08-25
client/doug_test/GDXDSD-7112/looker_dashboards/looker_user_facts.2024-08-25
Check to see if the four new files appear in the s3 client bucket: https://ca-central-1.console.aws.amazon.com/s3/buckets/sp-ca-bc-gov-131565110619-12-microservices?region=ca-central-1&bucketType=general&prefix=client/doug_test/GDXDSD-7112/looker_dashboards/&showversions=false