At the moment, we tag all resources generated by ZDM with a Name AWS Tag and give the option to users to specify a custom suffix, which is appended to the Name tag value and also set as an additional Owner AWS Tag. This enables the user to easily view the ZDM resources and potentially distinguish different ZDM deployments that have been created in the same AWS account.
However, we could consider making this more flexible by allowing the user to specify multiple, customisable tags to be added to all resources that are being created for a certain deployment (i.e. the user would indicate any number of name and value pairs to be passed to Terraform).
Doing this in the Terraform part is straightforward, but we have to find a convenient and easy way for the user to provide this list in the run_terraform_zdm.sh shell script in a format that is not too cumbersome and error-prone.
┆Issue is synchronized with this Jira Task by Unito
┆Components: Automation
┆Priority: Major
At the moment, we tag all resources generated by ZDM with a
NameAWS Tag and give the option to users to specify a custom suffix, which is appended to theNametag value and also set as an additionalOwnerAWS Tag. This enables the user to easily view the ZDM resources and potentially distinguish different ZDM deployments that have been created in the same AWS account.However, we could consider making this more flexible by allowing the user to specify multiple, customisable tags to be added to all resources that are being created for a certain deployment (i.e. the user would indicate any number of name and value pairs to be passed to Terraform).
Doing this in the Terraform part is straightforward, but we have to find a convenient and easy way for the user to provide this list in the
run_terraform_zdm.shshell script in a format that is not too cumbersome and error-prone.┆Issue is synchronized with this Jira Task by Unito ┆Components: Automation ┆Priority: Major