feat: use local cache for storing tag information

[juev]

Fixed: #199

Since we add a local cache for 20 minutes to store information about golang tags, we can safely access the github api for information about tags. At the same time, we will not receive errors like too many requests.

Currently, the storage time in the cache is strictly specified in the program code and is 20 minutes. It is probably worth considering the ability to change this parameter in the future. If you consider it necessary, you can implement this in the current PR.

Also, adding a file with a local cache allows you to independently prepare this file in a number of environments and put it in the gobrew working directory. This will avoid additional requests to Github for tags. This is for question #197

I tested this solution locally.

[github-actions]

CoverItUp Report

Type	master	feature/use-cache	338c4a4 from a0caa73
coverage	59.6%	60.5%	📈
build-time	1sec	0sec	📉
go-binary-size	9.0kKB	9.6kKB	📈
go-mod-dependencies	28	28
go-sec-issues	10	12	📈
unit-test-run-time	18sec	19sec	📈
allocs-per-op	19.2kalloc	18.5kalloc	📉

Comparisons Chart - master from feature/use-cache

Commits History

Upto a0caa73 for #201

Users History

Upto a0caa73 for #201

Embed README.md

[github-actions]

CoverItUp Report

Comparison Table - 7 Types 📈

Type	master	feature/use-cache	338c4a4 from 99ea1a1
coverage	59.6%	60.5%	📈
build-time	1sec	0sec	📉
go-binary-size	9.0kKB	9.6kKB	📈
go-mod-dependencies	28	28
go-sec-issues	10	11	📈
unit-test-run-time	18sec	20sec	📈
allocs-per-op	19.2kalloc	18.5kalloc	📉

Comparisons Chart - master from feature/use-cache

Commits History

Upto 99ea1a1 for #201

Users History

Upto 99ea1a1 for #201

Embed README.md

[kevincobain2000]

Ok so you want to get rid of raw GitHub user json and replace it with the GitHub api.
There is however a problem with that when using gobrew on actions or Jenkins on ephemeral modes, since they don’t share the cache.

[kevincobain2000]

Just keep the raw GitHub user content. It never gave us any problems.

[juev]

Yes, I had doubts about that. Returned the prepared json back.

[github-actions]

CoverItUp Report

Comparison Table - 7 Types 📈

Type	master	feature/use-cache	338c4a4 from c31e0c5
coverage	59.6%	60.5%	📈
build-time	1sec	0sec	📉
go-binary-size	9.0kKB	9.6kKB	📈
go-mod-dependencies	28	28
go-sec-issues	10	11	📈
unit-test-run-time	18sec	20sec	📈
allocs-per-op	19.2kalloc	18.5kalloc	📉

Comparisons Chart - master from feature/use-cache

Commits History

Upto c31e0c5 for #201

Users History

Upto c31e0c5 for #201

Embed README.md

[kevincobain2000]

Just a thought. May be an option as --no-cache on cli to not use cache might do some good?
Or an option --clean-cache to bust the current cache.
It is 20 mins so no problems but might be a good compliance addition.

[juev]

Yes, it will need to be added. There is also an idea to configure the cache time. Leave 20 minutes by default, but with the ability to set any value.

I created a separate task so I wouldn't forget: #202