Bug report
Describe the bug
The deploy pipeline is failing on PRs opened from forks, because it cannot access API key (secrets are not shared with forks).

Is there a way around it? Or alternatively should we remove this workflow from PRs and have it only on main branch? What's the use-case for publishing from PRs?
To Reproduce
- Fork this repo
- Create a PR with any change
- Wait for deploy pipeline results - for example: https://github.com/agoda-com/net-loadbalancing/actions/runs/3443243315/jobs/5745853755
Expected behavior
Pipeline should be green.
Screenshots
Pipeline is red.

Bug report
Describe the bug
The deploy pipeline is failing on PRs opened from forks, because it cannot access API key (secrets are not shared with forks).

Is there a way around it? Or alternatively should we remove this workflow from PRs and have it only on main branch? What's the use-case for publishing from PRs?
To Reproduce
Expected behavior
Pipeline should be green.
Screenshots
Pipeline is red.
