-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Pipelines - Local Access, Product - Forge
-
Severity 3 - Minor
Issue Summary
When using the Get log file for a step API call in the forge app, it fails with 403 - BLOCKED_EGRESS error. Here is the sample code
const response = await api.asApp().requestBitbucket(
route`/2.0/repositories/${CONSTANTS.WORKSPACE_ID}/${repoSlug}/pipelines/${pipelineUuid}/steps/${stepUuid}/log`
);
Steps to Reproduce
- Create a Bitbucket Forge app
- Attempt to access the log file for a specific pipeline step using the Get log file for a step API endpoint and asApp() method
- Deploy and install the app
- observe the response.
Expected Results
The API should return the log file for the specified pipeline step, allowing access to the pipeline variable values present in the logs.
Actual Results
The API returns a 403 - BLOCKED_EGRESS error, preventing access to the log file for the pipeline step.
Workaround
- Add the egress to *.s3.amazonaws.com in manifest file. Ex:
external:
fetch:
backend:
- '*.s3.amazonaws.com'