Skip to content

s3 params should be profile specific #280

Description

@richford

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions