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
SSHA is limited to AWS support and I would use it with other public or private clouds.
I suggest to refactor the ssha package to separate the core and provider-specific plugins.
The core functionality (settings, menu, bastions, ssh) stays within SSHA and AWS-specific features (instance discovery, iam, ssm) can be placed in an AWS plugin. Later a GCP plugin or any other can be added. I plan to keep plugins in this repo but they can be moved out in the future.
The provider option will be added to the ssha block
ssha {
provider = "ssha.aws"
}
It will default to AWS so no changes in settings expected from users.
Ray, what are your thoughts on it? I can do the PR.
The text was updated successfully, but these errors were encountered:
Hi Alex. Sorry for the slow response, I only just noticed this.
This sounds good to me.
My only concern is adding extra dependencies that aren't used by all providers and making it "bloated." But pip supports something like pip install ssha[gcp] (example) to split out dependencies, so we can figure something out.
SSHA is limited to AWS support and I would use it with other public or private clouds.
I suggest to refactor the ssha package to separate the core and provider-specific plugins.
The core functionality (settings, menu, bastions, ssh) stays within SSHA and AWS-specific features (instance discovery, iam, ssm) can be placed in an AWS plugin. Later a GCP plugin or any other can be added. I plan to keep plugins in this repo but they can be moved out in the future.
The
provider
option will be added to the ssha blockIt will default to AWS so no changes in settings expected from users.
Ray, what are your thoughts on it? I can do the PR.
The text was updated successfully, but these errors were encountered: