-
-
Notifications
You must be signed in to change notification settings - Fork 337
Support for SSM Parameter Store Hierarchy #1128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
stale
Issue/PR is stale and closed automatically
Comments
Here is how we worked around the issue with our local copy. It may not be the best or most correct way, so I haven't submitted it as a PR yet:
|
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days. |
kayman-mk
added a commit
that referenced
this issue
Jul 22, 2024
## Description Using SSM parameter hierarchies (as described in https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-hierarchies.html) results in an error. See #1128 Several workarounds exist, but using `trimprefix` makes them superfluous. Having a `/` as first character results in the above mentioned error. ## Verification Checked the ARN of parameter `/test/test`. It showed up as `arn:aws:ssm:eu-central-1:123456789012:parameter/test/test` in the console. So no `//` at first place. --------- Co-authored-by: kirkchong <[email protected]> Co-authored-by: Matthias Kay <[email protected]> Co-authored-by: Matthias Kay <[email protected]>
Closed via #1146 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Using the latest version with the preregistered token workflow.
We're applying a hierarchy to our parameter names like described here: https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-hierarchies.html
Unfortunately that doesn't go well with the ssm policy created for accessing that parameter.
When the parameter is called "/terraform/prod/preregistered_gitlab_runner_token" the policy looks like this:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
As using a hierarchy is encouraged by AWS it would be awesome if this would be compatible with the module :)
Additional context
Thanks for you work!
The text was updated successfully, but these errors were encountered: