-
Notifications
You must be signed in to change notification settings - Fork 4k
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
pipelines: optionally provide access to the environment configuration for the self mutate stage #15279
Comments
Would be addressed by #15169 |
As #15169 only touches the BuildSpec I will implement this in a separate PR to not mix too many things. |
I think the specific use case mentioned in this issue is already possible with the @mrpackethead can you test if this solves the problem? |
Not sure if i missed that when i first setup my pipelines or if supportDockerAssets has been added in subsequent versions.. For that specific issue, it would resolve the issue and makes the container run in a prividlged mode ( so docker can run ). However it doestn allow me to adjust the other parameters of the environment ( such as size ).. Additinally ( a new want/requirement ) is that i want to specifiy the images that both the synth and update codebuilds will use, so that they use pre-canned images with all our dependancies already installed to speed up pipeline times.. |
I think all of this is addressed with the migration to the new cdk pipeline api |
|
Currently there is no exposed method for modifying the environment of the self mutate stage. In my use-case of pipeline i need to allow the self-mutate codebuild to run in privldiged mode. This is because my source stages use lambdas that are based on docker backed executables. ( in particuallar i do this so i can have a native integration with AzureDevops. )... I also set the compute_type to LARGE rather than SMALL as this improves the build times.. (
I currently do this by using escape hatches to set the Environment of the SelfMutation
I would propose creating something similar to pipelines.SimpleSynthAction , perhaps pipelines.SimpleMutateAction, which could be optionally added to the cdkpipeline.. There may be a case for providing a way to pass build/install commands similar to the simple synth..
The text was updated successfully, but these errors were encountered: