You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, not so much an issue as a feature request or question.
I am experimenting with using Actions + CDK to deploy a Lambda function with API Gateway, and as you probably know, on success the URL of the API is output as a "stack output" by CDK.
Is it currently possible, or could you consider making it possible, to somehow capture such stack outputs for re-use in the Action, perhaps as an environment variable?
Example use case: I deploy my api with gitops and would like to receive a Slack post (sent by the action) which includes the API url from the stack output later in the workflow on a successful deployment.
The text was updated successfully, but these errors were encountered:
cdk seems to output the line Outputs: followed by key-value pairs in the format key = value. Perhaps they could be mapped up to Action outputs generally, just passing through the CDK outputs as Action outputs (with a prefix?), and leaving the job of understanding them to the downstream jobs.
TBH I'll probably be doing this sort of thing with custom domain names most of the time anyway so I wouldn't consider this urgent, but it would be nice to have. Getting the stack outputs accessible might be pretty useful generally though,
Hi there, not so much an issue as a feature request or question.
I am experimenting with using Actions + CDK to deploy a Lambda function with API Gateway, and as you probably know, on success the URL of the API is output as a "stack output" by CDK.
Is it currently possible, or could you consider making it possible, to somehow capture such stack outputs for re-use in the Action, perhaps as an environment variable?
Example use case: I deploy my api with gitops and would like to receive a Slack post (sent by the action) which includes the API url from the stack output later in the workflow on a successful deployment.
The text was updated successfully, but these errors were encountered: