Amin Fazl
Amin Fazl
Is there a timeframe that this might get fixed?
Hi @eladb , My I get your feedback on this one?
I think this is the expected behaviour as the role assumption command, needs to have `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` to assume the role, and then will override them and also set...
Thanks @jessebye, had look at this a bit further and found out that there are two issues here: 1. We used `typescript.TypeScriptProject` in our repo and that generated `AWS_ROLE_TO_ASSUME`, and...
Potential fix for the first issue: https://github.com/projen/projen/pull/1846
Thanks @mrgrain for quick look at this. the workflow of upgrade is: 1. npm ci 2. some upgrades using npm-check-updates 3. npm i What is happening here is that if...
I agree, this is not a problem with projen, it is an issue with npm and how it handles things. give me some time and I will shoot through a...
Hi @mrgrain , I have tried to reproduce this issue in a public repo. I originally had only public packages in this repo and the upgrade task was working fine....
I have setup scoped packages to go through code artifacts, and the rest of the packages through npm. This is setup via scoped packages options, in projen. I have not...
My earlier comment was result of my investigation, I was not able to test that. But I have followed these steps by running them manually and it worked.