History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3900
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Robin Shen
Reporter: Lukasz Listewnik
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Secret value is no longer a secret in triggered configuration.

Created: 31/Oct/22 11:11 AM   Updated: 31/Oct/22 11:59 PM
Component/s: None
Affects Version/s: 12.0.2
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

 Description  « Hide

Reproduction steps:
- Create two configurations A and B
- In A:
    - Create Variable with value stored as secret
    - Create step that Triggers B configuration
    - In step that Triggers B configuration add created variable (our secret) to Variables list
- In B configuration create step that uses our secret variable from configuration A
- Run Build A

What happens:
- Variable passed by A configuration as secret is no longer a secret in B configuration (We can see the value of our secret variable in build page instead of "*****")

What should happen:
- Variable should still be treated as secret in B configuration

 All   Comments   Work Log   Change History      Sort Order:
Robin Shen [31/Oct/22 11:59 PM]
I guess you are passing variable value as ${vars.getValue("theSecretVar")}? In this case B has no means to know it is a secret. To work around this issue, just define a variable with same name in B (or move secret variable definition in A to common parent of A and B), to let B know it is a secret.