When running vagrant provision with the chef-golang recipe, it complains that the /var/chef/cache directory does not exist:

[2013-09-14T21:22:44+00:00] FATAL: Chef::Exceptions::EnclosingDirectoryDoesNotExist: remote_file[/var/chef/cache/go1.0.3.linux-amd64.tar.gz] (golang::install line 14) had an error: Chef::Exceptions::EnclosingDirectoryDoesNotExist: Parent directory /var/chef/cache does not exist.

Here's the longer stacktrace:

Generated at Sat Sep 14 21:30:13 +0000 2013
Chef::Exceptions::EnclosingDirectoryDoesNotExist: remote_file[/var/chef/cache/go1.0.3.linux-amd64.tar.gz] (golang::install line 13) had an error: Chef::Exceptions::EnclosingDirectoryDoesNotExist: Parent directory /var/chef/cache does not exist.
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/mixin/why_run.rb:248:in `run'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/mixin/why_run.rb:329:in `run'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/mixin/why_run.rb:328:in `each'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/mixin/why_run.rb:328:in `run'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/provider.rb:132:in `process_resource_requirements'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/provider.rb:109:in `run_action'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/resource.rb:593:in `run_action'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/runner.rb:49:in `run_action'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/runner.rb:81:in `converge'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/runner.rb:81:in `each'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/runner.rb:81:in `converge'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/resource_collection.rb:94:in `execute_each_resource'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/resource_collection/stepable_iterator.rb:116:in `call'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/resource_collection/stepable_iterator.rb:116:in `call_iterator_block'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/resource_collection/stepable_iterator.rb:85:in `step'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/resource_collection/stepable_iterator.rb:104:in `iterate'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/resource_collection/stepable_iterator.rb:55:in `each_with_index'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/resource_collection.rb:92:in `execute_each_resource'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/runner.rb:80:in `converge'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/client.rb:378:in `converge'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/client.rb:420:in `do_run'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/client.rb:176:in `run'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/application/solo.rb:230:in `run_application'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/application/solo.rb:218:in `loop'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/application/solo.rb:218:in `run_application'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/../lib/chef/application.rb:70:in `run'
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-10.14.2/bin/chef-solo:25
/opt/vagrant_ruby/bin/chef-solo:19:in `load'

Is there a plan to upgrade to 1.2.2? If yes, should I help ? If no, what's the reason :)?

👻 Brief Description

There's an attribute for node['golang']['scm'] but setting it to false does not result in git and mercurial being installed.

🥞 Cookbook version

4.1.0

👩‍🍳 Chef-Infra Version

15.15.0

🎩 Platform details

Operating system distribution and release version. Cloud provider if running in the cloud.

Steps To Reproduce

Steps to reproduce the behavior:

node.default['golang']['scm'] = false
include_recipe 'golang'

🚓 Expected behavior

Git and Mercurial are not installed.

Thanks folks!

🗣️ Foreword

Thank for taking the time to fill this feature request fully. Without it we may not be able to , and the issue may be closed without resolution.

🙍 Problem Statement

Application & system cookbooks, should follow the Sous-Chefs standards and use custom resources, and library helpers to install and configure software. This cookbook still uses attributes and recipes.

❔ Possible Solution

1. Introduce custom resources that are wrapped by the current recipes.
2. Add a warning to the recipes to use the custom resources directly
3. Deprecate/remove the current recipes

⤴️ Describe alternatives you've considered

Leave it as it is.

➕ Additional context

Add any other context about the problem here. e.g. related issues or existing pull requests.

There's not much you can do about this besides changing the meta name to chef-golang... but.. If the meta name does not match the directory name while using Vagrant, Chef complains that the template file does not exist in template/default/golang.sh.erb (it looks in /golang/templates/default/ for some reason)

This can be easily fixed by simply renaming the directory after cloning, but it's an annoying bug to have to troubleshoot and I bet I'm not the only one who's had to do so. Perhaps adding a warning in the README would suffice.

The use of the :go attribute in both this cookbook and https://github.com/ThoughtWorksInc/go-cookbook is problematic. Can a change be made on this cookbook updating the attribute to golang?

Things like ['go']['version'] are identical.

atm it always installs master and then never updates ...
I need to set it to a certain tag or sha ... is that possible ?

@mburns

...

Makes is more difficult to discern when a given release was cut.

Cookbook needs setting up for sous

• metadata
• terraform (admin)
• standard files (bot)
• cookstyle (bot)
• labels standardise (bot)
• github actions
• circleci (admin)
• rebase the files used

🗣️ Foreword

Thank for taking the time to fill this feature request fully. Without it we may not be able to , and the issue may be closed without resolution.

:person_frowning: Problem Statement

Currently has depends 'ark', '~> 5.0'
Ark has updates in 6.0 to support Chef 17
Request is to support Chef 17

❔ Possible Solution

Allow ark 6.x

⤴️ Describe alternatives you've considered

n/a

➕ Additional context

n/a

golang on Supermarket has only versions upto 1.7.0.
chef-golang on Supermarket is even older at 1.0.1 (2013)

I was wondering if it's possible to push v3 that's currently the latest on this repo to Supermarket and if it already is, where is it?

Thanks!!!

I used this cookbook to install Go 1.2rc5 by overriding the necessary attributes. Now I changed these attributes to update to Go 1.2, but the update did not happen.

I think the problem is the not_if attribute of the remote_file resource in the default recipe. It is not very exact, so version 1.2 also matches 1.2rc5 and the new archive will not be downloaded.

this is due to matching against

 not_if "#{node['go']['install_dir']}/go/bin/go version | grep #{node['go']['version']}"

🗣️ Foreword

Thank for taking the time to fill this feature request fully. Without it we may not be able to , and the issue may be closed without resolution.

:person_frowning: Problem Statement

We are missing a test for the install_dir property of the default resource.

❔ Possible Solution

A clear and concise description of what you want to happen.

⤴️ Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

➕ Additional context

Add any other context about the problem here. e.g. related issues or existing pull requests.

This commit f3a80b5 is not backwards compatible with Chef 11.10. The following happens:

Fetching 'golang' from https://github.com/NOX73/chef-golang.git (at master)
STDERR: The following error occurred while reading the cookbook `golang':
Ridley::Errors::FromFileParserError: Could not parse `/tmp/d20161006-11381-rcpqw8/metadata.rb': undefined method `source_url' for #<Ridley::Chef::Cookbook::Metadata:0x007f8acd0f1798>

Issues on other repos regarding this:
chef/chef#2937
https://github.com/agileorbit-cookbooks/java/issues/240

golang::packages tries to cache the package in the chef client cache directory, which is only writable by root:

      Recipe: golang::packages
         * golang_package[github.com/etsy/hound/cmds/...] action install
           * bash[Installing package github.com/etsy/hound/cmds/...] action run

             ================================================================================
             Error executing action `run` on resource 'bash[Installing package github.com/etsy/hound/cmds/...]'
             ================================================================================

             Mixlib::ShellOut::ShellCommandFailed
             ------------------------------------
             Expected process to exit with [0], but received '141'
             ---- Begin output of "bash"  "/tmp/chef-script20160620-579-420w5l" ----
             STDOUT:
             STDERR: /tmp/chef-script20160620-579-420w5l: line 1: /tmp/kitchen/cache/github.com-etsy-hound-cmds-...: Permission denied
             ---- End output of "bash"  "/tmp/chef-script20160620-579-420w5l" ----
             Ran "bash"  "/tmp/chef-script20160620-579-420w5l" returned 141

             Cookbook Trace:
             ---------------
             /tmp/kitchen/cache/cookbooks/golang/providers/package.rb:14:in `block in class_from_file'

             Resource Declaration:
             ---------------------
             # In /tmp/kitchen/cache/cookbooks/golang/providers/package.rb

        5:   bash "Installing package #{new_resource.name}" do
        6:     code "#{node['go']['install_dir']}/go/bin/go get -v #{new_resource.name} 2> >(grep -v '(download)$' > #{tmp_file_path})"
....

The cache file needs to be created with the correct ownership.

The README.md includes HTML formatting which is being displayed on the Supermarket.

Fix this by using only markdown in the README file. Are there other places where you require this HTML formatting?

👻 Brief Description

when I specify a package @ a tag, it complains " go: cannot use path@version syntax in GOPATH mode"

🥞 Cookbook version

v3.0.1

👩‍🍳 Chef-Infra Version

13.10.0

🎩 Platform details

ubuntu 18.04

Steps To Reproduce

Steps to reproduce the behavior:

1. put something like 'github.com/etsy/hound/cmds/[email protected]' into node.default['golang']['packages']
2. run the cookbook.

🚓 Expected behavior

get, build, install the binary

➕ Additional context

Add any other context about the problem here. e.g. related issues or existing pull requests.

Old repo and attributes names (golang vs. chef-golang) in Readme

🗣️ Foreword

👻 Brief Description

When using the go 1.18 version, the package installation is no longer working because packages cannot be installed globally using go get leading to this error message:

         go: go.mod file not found in current directory or any parent directory.
    	'go get' is no longer supported outside a module.
    	To build and install a command, use 'go install' with a version,
    	like 'go install example.com/cmd@latest'
    	For more information, see https://golang.org/doc/go-get-install-deprecation
    	or run 'go help get' or 'go help install'.

🥞 Cookbook version

version is 5.3.2 but this will fail in any version

👩‍🍳 Chef-Infra Version

chef version is 17.9.46 but this is not related.

🎩 Platform details

Operating system distribution and release version. Cloud provider if running in the cloud.

Steps To Reproduce

Steps to reproduce the behavior:

with a recipe using this cookbook:

• specify go 1.18 or above (in my case 1.18.1)
• specify a package to be installed using the node_attributes (in my case golangcilint)
• run chef on the instance and see the error message

🚓 Expected behavior

I expect the package that I specified in node attributes being installed globally without failure

➕ Additional context

I'm trying to make a pr to fix this issue, however I'm kind of a noob in ruby/chef so I might have questions :)

Adding a tag to match the metadata.rb would help with dependency management using Berkshelf. Current version seems to be 1.4.0. Thanks!

🗣️ Foreword

https://supermarket.chef.io/cookbooks/golang -> View Source goes to https://github.com/NOX73/golang

👻 Brief Description

https://github.com/NOX73/golang is gone

🥞 Cookbook version

3.0.0

Steps To Reproduce

Steps to reproduce the behavior:

1. Go to https://supermarket.chef.io/cookbooks/golang
2. Click on View Source
3. 404 not found

🚓 Expected behavior

Going to https://github.com/sous-chefs/golang

➕ Additional context

Looking at the changelog, it seems the repo from NOX73 was first renamed to chef-golang

Now that the metadata is up to date in v3.0.0, could you reset / update the source_url used by https://supermarket.chef.io/cookbooks/golang ?

Thanks

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Hi, I'd like to help maintain this cookbook and merge pending PRs. I've started using this at work and would rather maintain my fixes in a canonical place and not maintain a fork.

@NOX73 thoughts?

• Github collaborator
• Supermarket collaborator (?) to upload new releases

Cheers!