Have CI runs display unprotected ENV vars and their value in build log

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

We've just spent most of the week debugging an issue related to a buildpack URL that we would have solved in a few minutes if ENV vars were being displayed as part of CI runs.

Target audience

Persona: Software developer

Persona: DevOps Engineer

Further details

Proposal

Have ENV vars and their values displayed as part of CI build log, hide values for protected vars.

What does success look like, and how can we measure that?

ENV vars are being displayed in Build log

Links / references