Joris Conijn

Sounds good @sbkok!

We should consider adding additional access per project to the role. This should become possible if we switch to a role per project model. This would also help with granting...

Hi @sbkok, Yes I did had a look at the monorepo example, but that requires 2 pipelines and then you cannot pass the output of the first CloudFormation stack to...

```txt [Container] 2022/03/11 11:55:16 Running command cd ./subscription [Container] 2022/03/11 11:55:16 Running command python ../adf-build/generate_params.py Traceback (most recent call last): File "../adf-build/generate_params.py", line 17, in from resolver import Resolver File...

One solution would be replacing/appending the `${LAMBDA_TASK_ROOT}/adf-build/python` to the `PYTHONPATH`. This will then be part of the `generate_params.py` script. Would there be any concern doing this? If not I am...

Forgot to mention it but had a chat with @sbkok about the parameters. Hence I updated the issue description. I validated the use cases we have not all but looking...

@AndreasAugustin not quite, I encountered the timeout on a CodeBuild project. #371 is about Lambda timeouts. But you do raised a concern in ADF itself, there is no proper retry...

@ntwobike nice! I had one question, did you consider the following approach to eliminate 1 pipeline: ```yaml - name: custom-config-rules ## repo name default_providers: source: provider: codecommit properties: account_id: build:...

@ntwobike you will need a subfolder for example: `lambda` and `config-rules` then duplicate put the `params` folder and put them in those folders: ```yaml targets: - name: LambdaDeployment regions: .......

👌 Nice, that's a lot simpler! The CloudFormation parameters of both templates are the same I assume? And that is the reason you can use the `./adf-build/generate_params.py` in a normal...