-
Notifications
You must be signed in to change notification settings - Fork 686
feat(control-plane): [issue-4833] AWS SSM Parameter store tags #4834
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
base: main
Are you sure you want to change the base?
Changes from 4 commits
377d2a2
36f4f61
a9d685d
7361092
9bf790d
340a39a
3ac7b16
1590623
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| locals { | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @wadherv sorry for the long wait. Just test the PR with a small adjustment. But would first discuss the intended working. I see a fewo options, but looking for use cases.
I have adjust the this local.tf file for a quick check, optiotn 2. In this case paramters got the valures from var.tags applices. Since I have not set parameter_store_tags. What do you think. Are you looking for way have custom tags, or just getting the standard tags applices. When only adding the standard tag set in the module, we could even drop the introduced paramter (reducing complexity) and simply inject var.tags into the lambda.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @npalm For my requirement, I want to apply only the default set of tags to the SSM Parameter Store, while also providing users the option to add additional custom tags specific to SSM Parameter resources.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Something like below: |
||
| parameter_store_tags = "[${join(", ", [ | ||
| for key, value in var.parameter_store_tags : "{ key = \"${key}\", value = \"${value}\" }" | ||
| ])}]" | ||
| } | ||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -16,6 +16,7 @@ variable "config" { | |||||
| timeout = number | ||||||
| zip = string | ||||||
| subnet_ids = list(string) | ||||||
| parameter_store_tags = string | ||||||
|
||||||
| parameter_store_tags = string | |
| parameter_store_tags = map(string) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lambda function environment variable only accepts string, map value is converted into string at https://github.com/github-aws-runners/terraform-aws-github-runner/pull/4834/files/7361092dac821cbf6679bc7ae8966f1288b26169#diff-5c6c370f29fac62114adf0ecc2806bc009702bcf32f96bad61a8d40c17448462
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default value should be an empty array
[]instead of an empty object{}to match the expected type structure used in the scale-up function and maintain consistency.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed