Limit scope of installable content

ansible / mazer

Experimental Ansible Galaxy Content Manager

GNU General Public License v3.0

113 stars 18 forks source link

Limit scope of installable content #49

Closed chouseknecht closed 6 years ago

chouseknecht commented 6 years ago

There's still a lot of questions around modules and plugins, mainly the following:

How to prevent certain things being included in module_utils (i.e., basic.py)
How to handle name collisions
How to collect more metadata
How to handle dependencies

For this reason, we will limit for the v3.0 release of the client (not sure what version we're actually calling it, but the version we release at the end of June) what can be installed to the following:

Traditional roles
all roles from a multi-content repository
a single role from a multi-content repository

Support for modules and plugins will be included in the next release, assuming we have answers to the above questions.

chouseknecht commented 6 years ago

@alikins

As we discussed in chat, lets also do the following as part of this:

[x] Change the repo name to 'mazer'
[x] Change the repo license file, and README, to GPLv3
[x] Create a 'devel' or 'develop' branch, and set that to the default branch.
[x] There will be no 'master' branch, so rename or remove 'master'.
[ ] Move the module/plugin/module_utils install code to a branch other than the default. It needs to be off to the side for now. We'll bring it back once the product team is comfortable. If the code is not 'movable' or really straightforward to remove, let's at least make sure it's not easily detectable or documented. In other words, it shouldn't appear in any usage or help text, nor examples.

When we're ready to cut a release, we can simply use tags, or create a stable-x.y branch.

chouseknecht commented 6 years ago

The install code for modules, plugins, module_utils is not critical, and not tied to the v0.1.0 release. We're not removing the code, and we're not going to continue iterating on it for this release. If it doesn't work in v0.1.0, that's perfectly fine.

We will begin iterating on it again for v0.2.0, so let's not completely abandon it, or remove.

alikins commented 6 years ago

Default branch is now 'devel' and 'master' has been deleted. The repo license file, and README have been updated to GPLv3 repo is now named 'mazer'

alikins commented 6 years ago

Fixed in devel at sometime before 91262d9876c3d486c816b057f54a6a44affd19e1