You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm attempting to render some templates and populate some values with secrets from AWS Secrets Manager. I'm currently unable to use v4.x due to this issue: #2190 so I'm using v3.11.8. I'm able to pull secrets just fine, even from other AWS accounts so all good there. I am however, doing so in a suboptimal way when I need to pull secrets from more than one Secrets Manager path. What I'd like to do is specify Secrets Manager (no URI) as a data source and then specify the URI in the template like so:
But this fails with an error: error="yaml: line 3: mapping values are not allowed in this context". Adding /// to the datasource URL does not help. This is despite this working using stdin:
But I'd rather not have to configure a dedicated datasource for every secret I'd like to retrieve.
Very likely there's something I'm failing to understand here. If anyone has any pointers on what I may be doing wrong, I'd appreciate your input. Thanks
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
This is a great tool so thank you for making it.
I'm attempting to render some templates and populate some values with secrets from AWS Secrets Manager. I'm currently unable to use v4.x due to this issue: #2190 so I'm using v3.11.8. I'm able to pull secrets just fine, even from other AWS accounts so all good there. I am however, doing so in a suboptimal way when I need to pull secrets from more than one Secrets Manager path. What I'd like to do is specify Secrets Manager (no URI) as a data source and then specify the URI in the template like so:
But this fails with an error:
error="yaml: line 3: mapping values are not allowed in this context"
. Adding///
to the datasource URL does not help. This is despite this working using stdin:This does work:
But I'd rather not have to configure a dedicated datasource for every secret I'd like to retrieve.
Very likely there's something I'm failing to understand here. If anyone has any pointers on what I may be doing wrong, I'd appreciate your input. Thanks
Beta Was this translation helpful? Give feedback.
All reactions