Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

regular issue regarding gem dependencies faraday #137

Closed
3 tasks done
Grummfy opened this issue Sep 7, 2021 · 1 comment
Closed
3 tasks done

regular issue regarding gem dependencies faraday #137

Grummfy opened this issue Sep 7, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@Grummfy
Copy link

Grummfy commented Sep 7, 2021

Checklist

  • Upgrade Terraspace: last version
  • Reproducibility: almost at each terraspace update
  • Code sample: no specific to code

My Environment

Software Version
Operating System GNU/Linux Ubuntu 21.04
Terraform 1.0.4
Terraspace 0.6.13-20210902100211
Ruby 2.7.2p137

Expected Behaviour

When there is an update of terraspace, to have just some basic dependency to update

Current Behavior

When there is an update of terraspace, the installation require some update (OK), but most of the time I need to clear dependency to have a valid installation

"You have already activated faraday 1.7.0, but your Gemfile requires faraday 0.17.4. Prepending bundle exec to your command may solve this."

The issue seems to be related to faraday that are required in two different version (0.

Step-by-step reproduction instructions

  1. Create a project with terraspace, make sure everything run smoothly
  2. Wait for terraspace update
  3. Somme dependency issue will appears, update them individually or globally whatever) with "bundle update X"
  4. run terraspace check, see the error with faraday 0.17.4 & 1.7.0 following the dependency
  5. run bundle clean --force and bundle install to fix the issue

Solution Suggestion

Force some dependency or at least check compatibility. In #135 it's seems there is the same issue, but upgrade ruby seems to solve the issue.

Note

I'm not a ruby developer...

@tongueroo
Copy link
Contributor

tongueroo commented Dec 30, 2021

Bummer. Dug into this. Addressing this by improving the terraspace wrapper generated by the standalone installers. Details here:

You won't have to type bundle exec. Believe this should resolve the issues. 🧐

In addition, added a friendly usage message with instructions on how to resolve if the error occurs. PR: #177 The standalone installer's new shim, as of terraspace v1 includes this smarter shim already.

Also, remove terraspace_plugins_* out of terraspace core. #173 This should also mitigate gem dependency graph resolution issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants