GITHUB-ACTIONS · Question #34
As a DevOps engineer, you are trying to leverage an organization secret in a repo. The value received in the workflow is not the same as that set in the secret. What is the most likely reason for the
The correct answer is A. There is a different value specified at the rego level.. GitHub secrets are defined at different levels: organization, repository, and sometimes at the workflow level. If a secret is defined at both the organization level and the repository level, the repository-level secret will take precedence. So, if the value of the secret differs
Question
As a DevOps engineer, you are trying to leverage an organization secret in a repo. The value received in the workflow is not the same as that set in the secret. What is the most likely reason for the difference?
Options
- AThere is a different value specified at the rego level.
- BThere is a different value specified at the workflow level.
- CThe Codespace secret doesn't match the expected value.
- DThe Encrypt Secret setting was not configured for the secret.
- EThere is a different value specified at the enterprise level.
How the community answered
(34 responses)- A76% (26)
- B3% (1)
- C6% (2)
- D12% (4)
- E3% (1)
Explanation
GitHub secrets are defined at different levels: organization, repository, and sometimes at the workflow level. If a secret is defined at both the organization level and the repository level, the repository-level secret will take precedence. So, if the value of the secret differs between these levels, the workflow will use the value from the repository level instead of the organization level.
Topics
Community Discussion
No community discussion yet for this question.