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

Explicit plugins #81

Merged
merged 3 commits into from
Jan 31, 2019
Merged

Explicit plugins #81

merged 3 commits into from
Jan 31, 2019

Commits on Jan 25, 2019

  1. Add explicit-load versions of plugins

    The existing aws plugins install their metadata at package load
    time. They aren't meant to be loaded in test/development environments,
    but there is no good way to only load them in production since you
    can't conditionally load a package.
    
    - move the plugins under a new /awsplugins path and change init() to
      Init() so user must explicitly call a method to load the plugin.
    - leave the old plugins in place, delegating to the new plugins. i
      also left the "Origin" constants since those are part of the
      packages' public APIs.
    Muir Manders committed Jan 25, 2019
    Configuration menu
    Copy the full SHA
    c3385e1 View commit details
    Browse the repository at this point in the history
  2. Add myself to contributors

    Muir Manders committed Jan 25, 2019
    Configuration menu
    Copy the full SHA
    d0edaaa View commit details
    Browse the repository at this point in the history

Commits on Jan 31, 2019

  1. Add README.md note about new plugins

    Muir Manders committed Jan 31, 2019
    Configuration menu
    Copy the full SHA
    c38e224 View commit details
    Browse the repository at this point in the history