[foreman-dev] 1.15.4 - 1.16 RC.1 - 1.17 status

Hi all, Just a heads up on the status of all of the upcoming releases: - 1.15.4 - After doing all the cherry-picks, 1.15.stable went red in Jenkins https://github.com/theforeman/foreman/pull/4827 fixes it, after that is merged we should be able to start the usual build

Re: [foreman-dev] Bundler is unable to solve deps for fresh checkout

The easiest way to get the recent Gemfile.lock is to look at the build artifacts in jenkins jobs (also useful when investigating sudden test failures): http://ci.theforeman.org/job/test_develop/database=postgresql,ruby=2.4,slave=fast/ -- Ivan On Thu, Sep 14, 2017 at 3:34 PM, Ivan Necas

Re: [foreman-dev] Bundler is unable to solve deps for fresh checkout

What errors are you seeing. I've tried with ruby 2.2.2, and 2.3.1 bundler 1.15.4, everything worked fine. What gem --version do you have? Anything in `bundler.d/Gemfile.local.rb` that could be causing this? -- Ivan On Thu, Sep 14, 2017 at 3:13 PM, Lukas Zapletal wrote: > Hey,

Re: [foreman-dev] Re: [POC] Automatic inspection of user-created provisioning templates

Ewoud: About rack endpoint: It should be created for use case 2, where the check is running in "online"-ish mode. I prefer creating it as a microservice for scalability reasons, so I wouldn't want to tie it too tightly with foreman-templates. Besides that, tying it into foreman-templates will

[foreman-dev] Bundler is unable to solve deps for fresh checkout

Hey, when I do fresh foreman clone with clean Ruby version (tried 2.0.0 and 2.4.1), bundle install is not able to resolve dependencies and loops forever. I am using latest stable bundler, tried also pre1 version. Can someone confirm and provide a workaround? I think copying Gemfile.lock from

Re: [foreman-dev] Re: [POC] Automatic inspection of user-created provisioning templates

On Wed, Sep 13, 2017 at 12:05:49PM -0700, ssht...@redhat.com wrote: First attempt to create a design. It's an open discussion, everyone who wants to chime in, please do. The engine: will be deployed as a separate gem. My name suggestion the-detective

Re: [foreman-dev] Re: [POC] Automatic inspection of user-created provisioning templates

First, I don't think that this service has any secret information that should be kept under authorization/authentication. Even if we assume that some level of auth is indeed needed, the easiest way to implement it would be through Rack middleware. If the service is added to an application with

Re: [foreman-dev] Re: [POC] Automatic inspection of user-created provisioning templates

How would be the authentication/authorization work with this approach? - - Ivan On Wed, Sep 13, 2017 at 9:05 PM, wrote: > > First attempt to create a design. It's an open discussion, everyone who > wants to chime in, please do. > > The engine: will be deployed as a separate