From f16821cbb0eee1d3324d81e575989e879c020e90 Mon Sep 17 00:00:00 2001 From: Drew Minnear Date: Wed, 26 Feb 2025 13:07:40 -0500 Subject: [PATCH] add snippet about how to debug failures loading secrets --- content/learn/getting-started-secret-management.adoc | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/content/learn/getting-started-secret-management.adoc b/content/learn/getting-started-secret-management.adoc index 04c3b8128..df666a68a 100644 --- a/content/learn/getting-started-secret-management.adoc +++ b/content/learn/getting-started-secret-management.adoc @@ -112,6 +112,15 @@ secrets: ---- $ ./pattern.sh make load-secrets ---- +If this command fails, for whatever reason, you most likely will not get a helpful error message since we avoid logging sensitive information by default. +In this situation, it's often helpful to run the following command before you try loading the secrets again in order to see a more detailed error message. +[source,terminal] + ++ +---- +$ .export EXTRA_PLAYBOOK_OPTS='-e hide_sensitive_output="false" -vvv' +---- +*This is intended as a temporary debug measure and should not be part of a normal production workflow since it may very well log secrets to stdout.* . Verify the secret in the Vault UI. @@ -259,4 +268,4 @@ image::multicloud-gitops/config-demo-mysecret.png[Secret details] [IMPORTANT] ==== Remember to consult the official documentation at link:https://validatedpatterns.io/[Validated Patterns] for detailed information about specific features and advanced configurations. -==== \ No newline at end of file +====