Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Need to output all Env Variables at end of script

Open
  • Is something wrong?
#63 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

No source file, test, or entry point is named. Start by locating the CLI script completion path and any Portal output handling, then determine which environment variables are considered relevant. Done means the names and values are shown at the end of the workload in the console and/or Portal as specified.

Written by the indexing model from the issue text.

Description

enhancement innovation engine

In order to work with the CLI past deployment we need to be able to work with the environment variables.

In order to lookup items in the portal we need to know the values of those variables.

All relevant environment variables should be echoed to the consoler and/or the Portal so that customers can see both the names and the values. For example:

The configuration of this workload is:

ENV_1=First
ENV_2=Second
Env_3=Third
Dominant language
Go
Stars
40
Forks
27
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/InnovationEngine

All issues in Azure/InnovationEngine

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.