rahulkeluskar / scraper Goto Github PK

With Shashank's reference that it is not relevant to S3.

@RahulKeluskar take 80+.
@therajdeepbiswas take 80-.

Will discuss method over call.

Write some tests to make sure stuff doesnt break on any commit. We will run these tests from our action

Cheers on the significant performance from /aws-cli.txt

Let's aim to get the following specifics next -

• AWS S3 (already WiP under /aws-s3-cli.txt).
• AWS EC2.
• AWS API Gateway.
• AWS Loadbalancer.
• AWS RDS.
• YAML.
• Azure, GCP, etc. to be populated better in this list in order of priority.

Use github actions to commit and push the aws-cli text file to repo after scraping if there is a diff

Maintain a separate file with hard coded commands.
Some commands we will manually insert into the script files so then we maintain a separate file and then

1. First we use the scraper and get the content dynamically
2. We then append the hard coded stuff into that so on overwriting the file the manual additions are not lost. We also cant keep on appending because there might be some duplicate entries.

The current scraper uses hard coding to parse everything, we need to move to something like every cheat sheet has a generic parser. We may not accurately be able to fetch all data in all cases but it may be possible to fetch a lot more data this way