-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
ecs: ability to access tag parameter value of TagParameterContainerImage #13202
ecs: ability to access tag parameter value of TagParameterContainerImage #13202
Comments
…inerImage Allows you to use the tag elsewhere within the container definition (e.g. to inform monitoring services of the release version). fixes: aws#13202
Thanks for opening the issue @alastair-watts-avrios ! I agree this can be useful. I'd love to have a PR for this 🙂. I like the first version a little more (it's more consistent with the existing Not sure if you've seen it already, but just to make sure, our Contributing guide is here: https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md#linking-against-this-repository. Thanks, |
|
It would be useful to be able to easily access the value of the docker image tag on a
TagParameterContainerImage
. Currently one can only access the parameter name which is very difficult to work with. The parameter itself can only be access by getting round the typing onTagParameterContainerImage
and accessing theimageTagParameter
field directly.This change could give access to the whole parameter or just the value.
Use Case
Adding an environment variable with that version to the container should be easy and is very useful for having monitoring aware of what version is running. Basically useful whenever you want a CloudFormation to be able to see the version running.
Proposed Solution
add:
Other
add
or
to
TagParameterContainerImage
.Happy to submit a PR with the first soon (as I think it fits with the existing method (and the move away from using parameters) best.
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: