s3 params should be profile specific
Opened this issue · 0 comments
richford commented
Some users might want to use cloudknot with multiple profiles. The s3_bucket param in the cloudknot config is global (i.e. across profiles) which leads to name collisions when trying to set up cloudknot on multiple accounts.