"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "solr/solr-ref-guide/src/package-manager.adoc" between
solr-8.4.0-src.tgz and solr-8.4.1-src.tgz

About: Solr is the search platform from the Apache Lucene project. Its major features include full-text search, hit highlighting, faceted search, caching, replication, and a web admin interface.

package-manager.adoc  (solr-8.4.0-src.tgz):package-manager.adoc  (solr-8.4.1-src.tgz)
skipping to change at line 22 skipping to change at line 22
// //
// http://www.apache.org/licenses/LICENSE-2.0 // http://www.apache.org/licenses/LICENSE-2.0
// //
// Unless required by applicable law or agreed to in writing, // Unless required by applicable law or agreed to in writing,
// software distributed under the License is distributed on an // software distributed under the License is distributed on an
// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY // "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
// KIND, either express or implied. See the License for the // KIND, either express or implied. See the License for the
// specific language governing permissions and limitations // specific language governing permissions and limitations
// under the License. // under the License.
The package manager in Solr allows installation and update of Solr-specific pack ages in distributed and standalone environments. The package manager in Solr allows installation and updating of Solr-specific pa ckages in Solr's cluster environment.
In this system, a _package_ is a set of Java jar files (usually one) containing one or more <<solr-plugins.adoc#solr-plugins,Solr plugins>>. Each jar file is al so accompanied by a signature string (which can be verified against a supplied p ublic key). In this system, a _package_ is a set of Java jar files (usually one) containing one or more <<solr-plugins.adoc#solr-plugins,Solr plugins>>. Each jar file is al so accompanied by a signature string (which can be verified against a supplied p ublic key).
A key design aspect of this system is the ability to install or update packages in a cluster environment securely without the need to restart every node. A key design aspect of this system is the ability to install or update packages in a cluster environment securely without the need to restart every node.
Other elements of the design include the ability to install from a remote reposi tory; package standardization; a command line interface (CLI); and a package sto re. Other elements of the design include the ability to install from a remote reposi tory; package standardization; a command line interface (CLI); and a package sto re.
This section will focus on how to use the package manager to install and update plugins. This section will focus on how to use the package manager to install and update packages.
For technical details, see the section <<package-manager-internals.adoc#package- manager-internals,Package Manager internals>>. For technical details, see the section <<package-manager-internals.adoc#package- manager-internals,Package Manager internals>>.
== Interacting with the Package Manager == Interacting with the Package Manager
The package manager CLI includes allows you to: The package manager CLI includes allows you to:
* Start Solr with support for package management * Start Solr with support for package management
* Add trusted repositories * Add trusted repositories
* List packages at a repository * List packages at a repository
* Install desired packages * Install desired packages
skipping to change at line 161 skipping to change at line 161
[source,bash] [source,bash]
---- ----
$ bin/solr package deploy mypackage:2.0.0 --update -collections mycollection $ bin/solr package deploy mypackage:2.0.0 --update -collections mycollection
---- ----
You can run the `list-deployed` command to verify that this collection is using the newly added version. You can run the `list-deployed` command to verify that this collection is using the newly added version.
== Security == Security
As noted above in the section <<Add Trusted Repositories>>, the `add-repo` step should only be executed using an HTTPS endpoint in Solr (all other steps can be executed using HTTP - see also <<package-manager-internals.adoc#package-manager- internals,Package Manager Internals>>). This step registers the public key of th e trusted repository, and hence can only be executed using the package manager ( CLI) having direct write access to ZooKeeper. It is critical to protect ZooKeepe r from unauthorized write access. The `add-repo` step should only be executed using HTTPS enabled repository urls only so as to prevent against MITM attacks when Solr is fetching the public key for the repository. This `add-repo` step registers the public key of the trusted repository, and hence can only be executed using the package manager (CLI) havi ng direct write access to the trusted store of the package store (a special loca tion in the package store that cannot be written to using the package store APIs ). Also, it is critical to protect ZooKeeper from unauthorized write access.
Also, keep in mind, that it is possible to install *any* package from a reposito ry once it has been added. If you want to use some packages in production, a bes t practice is to setup your own repository and add that to Solr instead of addin g a generic third-party repository that is beyond your administrative control. Also, keep in mind, that it is possible to install *any* package from a reposito ry once it has been added. If you want to use some packages in production, a bes t practice is to setup your own repository and add that to Solr instead of addin g a generic third-party repository that is beyond your administrative control. Y ou might want to re-sign packages from a third-party repository using your own p rivate keys and host them at your own repository.
 End of changes. 4 change blocks. 
3 lines changed or deleted 3 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)