Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate extending Fogg to also spin-up in AWS #47

Open
Badgerati opened this issue Jun 5, 2017 · 3 comments
Open

Investigate extending Fogg to also spin-up in AWS #47

Badgerati opened this issue Jun 5, 2017 · 3 comments

Comments

@Badgerati
Copy link
Owner

Bit of a big one, but investigate the feasability of allowing Fogg to also spin-up infrastructure in AWS. I've eyed over the docs, and it seems possible.

Useful links:

@Badgerati
Copy link
Owner Author

Before getting into this, some heavy refactoring of Fogg is required first. This will be to move all Azure core commands to their own sub-module, so that AWS can have its own module.

That way, depending on the "provider" passed in a template, Fogg can import the relevant module, where call functions have the same name. Bit like Classes and Interfaces.

@Badgerati
Copy link
Owner Author

In fact, looking at it, could probably also do Google Cloud as well. Though... that'd be much later on

@Badgerati
Copy link
Owner Author

AWS module install: Install-Module AWSPowerShell

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

No branches or pull requests

1 participant