iamolegga

## Coverage report ### Total coverage | Status | Category | Percentage | Covered / Total | | :----: | :--------- | :--------- | :-------------: | | 🟢 | Statements...

Hello, thanks for PR. Before merging it I have a couple of questions: 1. Can you please provide a bit more info, I just didn't get it how is this...

All right, then I'll try to find time soon to add test to check if this close #8

@grehovm sorry, this is not a prioritized project for me at the moment, if you can add a test for this I'll merge and make a new release

Would love to make a review of pull request with this

Anyway for those who struggle I found a workaround, make a separate workflow with ``` on: workflow_run: types: [completed] workflows: [Original workflow] ``` then the cache is created successfully.

I create release (= git tag) on _main_ branch, within this release workflow I create cache, this is still _main_ branch. But this cache on _main_ branch which creation was...

For me it's not clear that cache created on default branch is not accessible for child branches when it's created by the tag. It's up to you, if you believe...

Also if you want I can help with configuring ci/cd for testing and package deploying

Are there any plans for autopilot support in Managed Service for Prometheus? If so what's the ETA? I have to decide if it worth to wait for it or go...