-
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
(apprunner): startCommand and environment are ignored in imageConfiguration #16812
Comments
I am working on the PR to fix this. |
Hey @pahud, have you been able to work on this? |
Yes. I'll create the PR today and link back to this issue. |
…iguration (#16939) This PR addresses the following issues 1. custom environment variables and start commands should be allowed for `imageConfiguration` 2. buildCommand, environment and startCommand should be allowed for `codeConfigurationValues` Fixes: #16812 - [x] add tests - [x] implementation ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
…iguration (aws#16939) This PR addresses the following issues 1. custom environment variables and start commands should be allowed for `imageConfiguration` 2. buildCommand, environment and startCommand should be allowed for `codeConfigurationValues` Fixes: aws#16812 - [x] add tests - [x] implementation ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…iguration (aws#16939) This PR addresses the following issues 1. custom environment variables and start commands should be allowed for `imageConfiguration` 2. buildCommand, environment and startCommand should be allowed for `codeConfigurationValues` Fixes: aws#16812 - [x] add tests - [x] implementation ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
What is the problem?
The
startCommand
andenvironment
are ignored in theimageConfiguration
.Reproduction Steps
What did you expect to happen?
the two properties should be properly configured..
What actually happened?
not configured in the synthesized cfn template
CDK CLI Version
1.126.0
Framework Version
No response
Node.js Version
v14.17.6
OS
mac os x
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: