You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like it would be nice to not have to merge potentially failing code just to check if it passes tests or not.
As far as I can tell so far, you need to have valid credentials in order cdk synth, which is required for sam local testing, but it's entirely possible I'm wrong here. It does seem like it should only require an account_id as opposed to the full access keys for deployment, but it would obviously be safer not to expose anything.
I'm hopeful we could find possible solutions on the CDK side, or by having a dedicated branch for testing PRs, etc. I'm not sure what the best approach here might be. What do you think?
The text was updated successfully, but these errors were encountered:
It seems like it would be nice to not have to merge potentially failing code just to check if it passes tests or not.
As far as I can tell so far, you need to have valid credentials in order
cdk synth
, which is required forsam local
testing, but it's entirely possible I'm wrong here. It does seem like it should only require anaccount_id
as opposed to the full access keys for deployment, but it would obviously be safer not to expose anything.I'm hopeful we could find possible solutions on the CDK side, or by having a dedicated branch for testing PRs, etc. I'm not sure what the best approach here might be. What do you think?
The text was updated successfully, but these errors were encountered: