Policy evaluation should able to validate the value attribute for Reference type secret.
complete
T
Tremendous Wildebeest
This request is the continuation of the ticket https://support.harness.io/hc/en-us/requests/73818. Policy couldn't validate the value(secret key) when the secret is Reference type but we need to enforce the prefix when they use the AWS Secret Manager(reference type) in order to protect the cross access.
Log In
A
Abhishek Thamman
complete
A
Abhishek Thamman
@Tremendous Wildebeest Rubber Scallop this is now shipped as part of Version 1.89.x (https://developer.harness.io/release-notes/platform/#version-189x-)
This post was marked as
in progress
Prateek Mittal
under review
R
Rubber Scallop
Feature Request
If Secret Definition Yaml has valueType: Reference, then include the Value.
secret:
type: SecretText
name: sns
identifier: sns
orgIdentifier: AWMAE
projectIdentifier: Renga
description: ""
spec:
secretManagerIdentifier: harnessSecretManager
valueType: Reference
[MISSING/REQUEST] value: /application/harness/<org>/<project>/<actual_secret_key>