Reserve "cog" bundle name for future use #817
Assignees
Milestone
Comments
christophermaier
added a commit
that referenced
this issue
Jun 25, 2016
To avoid confusion between "official" Operable-authored bundles and 3rd party bundles, we'll block the installation of bundles named * `cog` * `cog-*` * `operable-*` The bundle names `site` and `user` continue to be reserved for internal usage. The embedded bundle continues to be named "operable", and continues to be uninstallable by outside sources. We were using "cog" as a bundle name for testing data; obviously that's out now, so we'll now call it "test-bundle" instead. Fixes #817
christophermaier
added a commit
that referenced
this issue
Jun 28, 2016
While we don't currently have a "cog" bundle, we may provide one in the future. To preserve for that possibility, and to prevent possible confusion with 3rd party bundles that might arise, we're going to prevent bundles named "cog" from being installed for now. We were using "cog" as a bundle name for testing data; obviously that's out now, so we'll now call it "test-bundle" instead. Fixes #817
kevsmith
changed the title
cog bundle name for future use
kevsmith
changed the title
cog bundle name for future use
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should prevent the installation of any bundles named
"cog","cog-*", or"operable-*"to prevent confusion between "official" bundles from Operable itself and 3rd party bundles.Should we decide to create any bundles with those names in the future, we can revisit the blocking logic.
The text was updated successfully, but these errors were encountered: