Capture what-if output from stdout
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- azure, github-actions, typescript
Research direction
Start by reviewing the Azure Deploy GitHub Action's handling of what-if deployment output and its documentation. Determine whether stdout can be exposed as an output for workflow summaries, pull requests, or artifacts, and document or implement the supported capture path with an example showing the resulting value.
Written by the indexing model from the issue text.
Description
Hello,
Running a what-if deployment produces the below output in the standard output:
Is there any way to capture this to use somewhere else?
I'd like to include the result of the what-if operation in the workflow summary so that the users won't have to find buried in a step of the workflow.
Other uses that I can imagine for this also include printing the what-if in a pull request or save an artifact with infra changes.
I couldn't find it in the documentation, so if this is already supported, could you point me where to find the information? If not, could it be an addition?
Thank you.
- Dominant language
- TypeScript
- Stars
- 66
- Forks
- 20
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 22
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/bicep-deploy
-
Bicep Deploy task masks RestError when `details` is undefinedPossibly taken @anthony-c-martin claimed this 6 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Azure/bicep-deploy#350 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/bicep-deploy#309 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/bicep-deploy#347 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Azure/bicep-deploy#328 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Azure/bicep-deploy#322 ·
Maintainers usually reply within 1 day
All issues in Azure/bicep-deploy
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Graphify-Labs/graphify#4860 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sveltejs/eslint-plugin-svelte#1615 ·
Maintainers usually reply within 7 days
-
Parallel reticle_verify opens per-flow leases without the source lease's ignoreHTTPSErrorsPossibly taken @as992949791 claimed this today. Opengood first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
reticlehq/reticle#2033 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day