Downloads:

5,094

Downloads of v 1.4.1.20160127:

277

Last Update:

28 Jan 2016

Package Maintainer(s):

Software Author(s):

  • https://github.com/elasticsearch/elasticsearch/contributors

Tags:

Elastic Search Service

Elastic Search Service Install

This is not the latest version of Elastic Search Service Install available.

1.4.1.20160127 | Updated: 28 Jan 2016

Downloads:

5,094

Downloads of v 1.4.1.20160127:

277

Software Author(s):

  • https://github.com/elasticsearch/elasticsearch/contributors

Elastic Search Service Install 1.4.1.20160127

This is not the latest version of Elastic Search Service Install available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Elastic Search Service Install, run the following command from the command line or from PowerShell:

>

To upgrade Elastic Search Service Install, run the following command from the command line or from PowerShell:

>

To uninstall Elastic Search Service Install, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade elasticsearch-service -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade elasticsearch-service -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure elasticsearch-service installed
  win_chocolatey:
    name: elasticsearch-service
    state: present
    version: 1.4.1.20160127
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'elasticsearch-service' do
  action    :install
  version  '1.4.1.20160127'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: elasticsearch-service,
    Version: 1.4.1.20160127,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller elasticsearch-service
{
   Name     = 'elasticsearch-service'
   Ensure   = 'Present'
   Version  = '1.4.1.20160127'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'elasticsearch-service':
  provider => 'chocolatey',
  ensure   => '1.4.1.20160127',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install elasticsearch-service version="1.4.1.20160127" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator ferventcoder on 28 Jan 2016.

Description

Installs Elastic Search as a service from the elasticsearch package.


tools\chocolateyInstall.ps1
$path = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$path = (Join-Path ((get-item $path).parent.parent.FullName) -childPath elasticsearch\tools\*\bin)
$path = (gci $path\service.bat)
$javaHomeEnvName = "JAVA_HOME"

if($path -ne $null)
{
	$javaHome = [Environment]::GetEnvironmentVariable($javaHomeEnvName)
	if($javaHome -eq $null)
	{
		#Try get from registry
		$javaHome = (get-itemproperty "hklm:\SYSTEM\CurrentControlSet\Control\Session Manager\Environment").JAVA_HOME

		#If not in registry, look inside program files, then inside program files x86
		if($javaHome -eq $null)
		{
			if(test-path "C:\Program Files\Java")
			{
				$jreFolders = [System.IO.Directory]::GetDirectories("C:\Program Files\Java", "jre*",
									[System.IO.SearchOption]::TopDirectoryOnly)
									
				if($jreFolders.Count -gt 0)
				{
					$javaHome = $jreFolders | select -last 1
				}
				elseif(test-path "C:\Program Files (x86)\Java")
				{
					$jreFolders = [System.IO.Directory]::GetDirectories("C:\Program Files (x86)\Java", "jre*",
									[System.IO.SearchOption]::TopDirectoryOnly)
									
					if($jreFolders.Count -gt 0)
					{
						$javaHome = $jreFolders | select -last 1
					}
				}
			}
		}


		if($javaHome -ne $null)
		{
			[Environment]::SetEnvironmentVariable($javaHomeEnvName, $javaHome, [System.EnvironmentVariableTarget]::Machine);
			[Environment]::SetEnvironmentVariable($javaHomeEnvName, $javaHome, [System.EnvironmentVariableTarget]::User);
			[Environment]::SetEnvironmentVariable($javaHomeEnvName, $javaHome, [System.EnvironmentVariableTarget]::Process);
		}
	}
	
	$path = ($path[0]).FullName

	Install-ChocolateyEnvironmentVariable "ES_START_TYPE" "auto"
		
	&"$path" "install"
}
tools\chocolateyUninstall.ps1
$path = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$path = (Join-Path ((get-item $path).parent.parent.FullName) -childPath elasticsearch\tools\*\bin)
$path = (gci $path\service.bat)

if($path -ne $null)
{
$path = ($path[0]).FullName

&"$path" "remove"

}

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Elastic Search Service Install 1.4.1.20160202 267 Tuesday, February 2, 2016 Approved
Elastic Search Service Install 1.4.1.20160127 277 Thursday, January 28, 2016 Approved

Discussion for the Elastic Search Service Install Package

Ground Rules:

  • This discussion is only about Elastic Search Service Install and the Elastic Search Service Install package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Elastic Search Service Install, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus