http-request-action | Create HTTP Requests in GitHub Actions | REST library
kandi X-RAY | http-request-action Summary
kandi X-RAY | http-request-action Summary
Create HTTP Requests from GitHub Actions. This action allows GitHub events to engage with tools like Ansible AWX that use HTTP APIs.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Wrap protocol methods
- Redirect request .
- Checks if the current route is enabled .
- Iterates over iterator results
- Checks a module .
- connect the tunnel
- Runs iterator over provided array elements
- Runs iterator in series
- Iterate over an object
- Creates a new redirectable request .
http-request-action Key Features
http-request-action Examples and Code Snippets
Community Discussions
Trending Discussions on http-request-action
QUESTION
I'm new to GitHub Actions (and yaml syntax) so I may be misunderstanding something about the ability to pass data between jobs: I've been trying to use a workflow with two jobs:
- authenticateWithAuth0API asks for a token to be generated
- triggerNetlifyFunction uses the token to authenticate with a Lambda function
For the first job, I can see that I do get back some kind of response that is saved as an output. The logs show the response is an access token with value ***. I assume the value appears as asterisks in the logs because the runner understands this value to be sensitive (a secret - though not a GitHub Secret).
I was under the impression that I could declare this as an output (which seems to go through ok) and then use it in the next job with the "needs" context. I'm using it as the value to the "Authorization" header for a call triggered in the next job.
However, in the logs I can see that the value of the header is empty showing up as Authorization:"". Am I missing something in terms of the ability to pass sensitive variables between jobs?
...ANSWER
Answered 2021-Aug-24 at 20:23Added debug logs... if i'm reading this correctly it seems that my output variable token is not a string, it's an object
{access_token: *** }
? But even so, why would it come up as""
(empty string in the authorization header)? Should it not have added an object at least?
I believe this is an expected behaviour as Github Actions runner probably can't check the output value, and ensure the secret isn't exposed through the workflow afterwards.
A workaround to your issue could be to save the output (API_RESPONSE) as a secret on the first job, and then access it as any other secret on the second job.
This GH secrets action could help you do it (it would even update the secret if it is already set).
Note: There may be other actions available providing a similar result.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install http-request-action
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page