Re: [foreman-dev] Re: Discourse - upcoming dates

Dne neděle 10. prosince 2017 23:06:19 CET, Greg Sutcliffe napsal(a): > Just a short update on this - tomorrow is the day on my date list for > the announcement, but today is actually T-3weeks, so I'll be sending > that out to both lists in just a few minutes. > > The result, as I spoke about on

Re: [foreman-dev] Kanban tools and redmine

Dne středa 29. listopadu 2017 9:05:28 CET, Lukas Zapletal napsal(a): > Can you elaborate on why something does not make sense to track in > RedMine? I am not following, RedMine is a generic ticketing system and > you can create as many tickets as you want, e.g. Buy milk. It will > work. This is a

Re: [foreman-dev] Proposal: Foreman 1.18 = 2.0

Dne středa 29. listopadu 2017 14:36:18 CET, Ewoud Kohl van Wijngaarden napsal(a): > On Wed, Nov 29, 2017 at 02:18:35PM +0100, Lukas Zapletal wrote: > >> Bikeshedding about SemVer aside, I'm good with doing a 2.0 release in > >> the near future, but *please* lets use it to deprecate / drop stuff

Re: [foreman-dev] Re: [UX] Facets and Host UI - roadmap discussion.

You're right, there are cases where it's better to separate facets and cases where it's better to combine them. While we can define what page belongs to which category I think more natural approach is simply say that we need to allow both. For me, provisioning a host is a combination of

Re: [foreman-dev] speeding up tests

On úterý 7. listopadu 2017 11:12:31 CET Ivan Necas wrote: > On Tue, Nov 7, 2017 at 9:19 AM, Ohad Levy wrote: > > Hi, > > > > The challenge: > > > > As a developer, I feel under utilized waiting for tests, the current test > > suite for foreman core takes over an hour,

Re: [foreman-dev] [Event] Foreman Community Demo Items - Thu 16 Nov 3pm [BST]

I think there are some demo worthy PRs merged, is there a volunteer to demo them if they don't appear on agenda? I could take some. -- Marek On čtvrtek 9. listopadu 2017 13:28:23 CET Ori Rabin wrote: > Hi all, > > Demo time! As always, have a think for items which have been completed since >

[foreman-dev] Abandoned plugins under theforeman github org

Hello there thanks to Tomer and Timo, we were able to fix most of plugins after FactoryGirl was renamed to FactoryBot, see [1] for current status. As part of that, I found two plugins where we didn't get any response and they seem abandoned. Would it make sense to remove them from the foreman

Re: [foreman-dev] Foreman instrumenting analysis

On úterý 7. listopadu 2017 14:56:05 CET Eric D Helms wrote: > On Thu, Nov 2, 2017 at 5:05 PM, Ivan Necas wrote: > > I lean towards the push model here. The main reason is > > the simpler way to publish the instrumentation data from whatever > > process we want to track. Also,

Re: [foreman-dev] FactoryGirl renamed to FactoryBot - plugin maintainer action needed

On středa 1. listopadu 2017 10:19:08 CET Tomer Brisker wrote: > Hello, > This has now been merged in Foreman core. > All plugins should make sure that their respective PRs pass tests and > merge them now. If you need assistance making this change in your > plugin, please reach out to us and we

Re: [foreman-dev] 1.17 schedule

I think the date is reasonable. Given we have 2-3 RCs per 2 weeks, we could expect 1.17 release early next year right? Which I think is good since we'll have time to fix potential blockers after we're back from Christmas time off. -- Marek On úterý 31. října 2017 12:59:12 CET Ohad Levy wrote:

Re: [foreman-dev] Re: Database and Service Actions in RPM Post Scripts

I'd be in favor of a change and avoid running scripts in post scripts. This is the reason why we added "Optional Step 3 (C) - Run foreman-installer" to our manual [1] a long time ago. We recommend running installer after upgrade if users use it for initial setup. If this is too heavy step,

Re: [foreman-dev] Help needed: Discovery develop broken (Rails 5)

On čtvrtek 21. září 2017 9:46:59 CEST Lukas Zapletal wrote: > Hello, > > we are getting errors in discovery develop due to Rails 5 update: > > ActiveRecord::SubclassNotFound: Invalid single-table inheritance type: > Host::Discovered is not a subclass of Host::Managed > >

[foreman-dev] How to print a date/time in Foreman

Hello devs, a PR that unifies the way how we print the date/time information in Foreman was merged recently [1], it will be present in 1.16 release. If you're a plugin author or will ever need to print a date/time please use one of the following helper date_time_absolute(time, format =

Re: [foreman-dev] Plugin gems with a single author

On pondělí 11. září 2017 14:02:06 CEST Greg Sutcliffe wrote: > On Sun, 2017-08-20 at 16:33 +0200, Timo Goebel wrote: > > I'd also be interested in helping with foreman_bootdisk. Although > > it's sad to see, it looks like Dominic isn't maintaining this at all > > anymore. > > On Mon, 2017-08-21

Re: [foreman-dev] Permissions cleanup

On pondělí 11. září 2017 13:41:02 CEST Greg Sutcliffe wrote: > Hi all, > > In the context of the plugins-bus-factor discussion, etc, it occurred > to me that we still have a lot of people with access who aren't really > active any more - this can make it hard to see where action is needed. > >

Re: [foreman-dev] What is the process to get new resources added to transifex?

I think we don't have to follow the full-blown nomination process here, any concerns regarding giving Bryan admin access? Please let me know here or privately, otherwise I'll add Bryan in few days. -- Marek On pátek 8. září 2017 22:31:48 CEST bk wrote: > Also... hammer-cli-foreman-tasks..

[foreman-dev] Foreman core tests broken

Hello There's a new issue in core tests. Following failure can be observed in the whole matrix. UserTest.test_0066_can search users by usergroup ActiveRecord::StatementInvalid: PG::UndefinedColumn: ERROR: column "member_type" does not exist... It seems be caused by the new scoped_search

Re: [foreman-dev] [infra] Packaging reorganization

Perhaps the foreman_scap_client could be one. There's the gem itself [1] and configuring puppet module that we also package [2] [1] https://github.com/theforeman/foreman-packaging/tree/rpm/1.16/rubygem-foreman_scap_client [2]

Re: [foreman-dev] [Infra] Proposal to Move Jenkins Job Configurations

On sobota 2. září 2017 1:27:23 CEST Eric D Helms wrote: > Howdy, > > Some quick background, for those that don't know a majority of our Jenkins > job configuration are stored in git. I find our Jenkins job configuration > to be important for developers to be able to understand and contribute >

Re: [foreman-dev] Test failures and merging PRs

Thanks Timo for your input. Please see my comment below in the text. On čtvrtek 31. srpna 2017 23:08:34 CEST Timo Goebel wrote: > Am 28.08.17 um 17:12 schrieb Marek Hulán: > > 1) codeclimate is red > > > > This can be ignored, we never agreed on using this as a hard metr

Re: [foreman-dev] [Infra] Reducing Test Matrix

+1 -- Marek On středa 30. srpna 2017 12:36:01 CEST Ivan Necas wrote: > +1 > > -- Ivan > > On Wed, 30 Aug 2017 at 11:18, Lukas Zapletal wrote: > > Can we do similar for test_plugin_matrix? > > > > I'd like to propose additional change for plugins - to only run core > > tests

[foreman-dev] Test failures and merging PRs

Hello devs, since there was a discussion on foreman-dev IRC channel recently about merging PRs in Foreman core even if there's some build failed, I talked to few people and decided to describe here what I think is current way of how it works. I'm also attaching one suggestion at the end that

Re: [foreman-dev] Plugin gems with a single author

On pátek 18. srpna 2017 13:48:06 CEST Greg Sutcliffe wrote: > Hi all, > > As per the newly-merged plugin policy, I've taken a quick pass over all > the gems listed in the RPM packaging (which is more comprehensive than > the Deb packaging), grepped for "foreman" and "proxy", and then used > the

Re: [foreman-dev] Taking over plugins - do we need a policy?

On pondělí 14. srpna 2017 17:31:00 CEST Greg Sutcliffe wrote: > Hi all, > > This went fairly quiet, but we all seem largely in agreement. I'll > draft something up for the website and send a PR tomorrow. I had a few > side questions though: > > On Wed, 2017-07-19 at 10:

Re: [foreman-dev] Aligning Foreman & Katello git repositories

+1 for every suggestion! Which would you like to start with? I'd be interested in helping with forklift being used in jenkins for running bats tests. Later I hope with installers merge. -- Marek On středa 2. srpna 2017 14:33:44 CEST Ewoud Kohl van Wijngaarden wrote: > Hello all, > > As many

Re: [foreman-dev] Taking over plugins - do we need a policy?

On úterý 18. července 2017 13:15:22 CEST Greg Sutcliffe wrote: > Hi all, > > I've been thinking for a while about plugins, and how to continue them > when original authors move on. It's only natural that developers will > come and go, so we need to think about how to deal with this. We've got > a

Re: [foreman-dev] Re: plugin configuration management

On úterý 18. července 2017 12:15:37 CEST Fairouz el ouazi wrote: > HI, >PLease howa can make GET or Post request on my new plugin ? > > Le mercredi 12 juillet 2017 17:21:49 UTC+2, Fairouz el ouazi a écrit : > > Hi , > > > > I want to know if foreman plugin (ansible or chef )

Re: [foreman-dev] plugin configuration management

Hello, ansible plugin does not contact any external service to my knowledge except for smart proxy, chef plugin uses REST API to talk to smart proxy which then uses REST API to talk to chef server. Hope this helps -- Marek On středa 12. července 2017 17:21:49 CEST Fairouz el ouazi wrote: >

Re: [foreman-dev] Re: Plugins configuration managment platform

> existent configuration and having inventory . > > Le lundi 3 juillet 2017 09:16:05 UTC+2, Marek Hulán a écrit : > > Hello > > > > the smart proxy chef plugin is only a proxy between Foreman - chef-client > > and > > Foreman - chef-server. Most

Re: [foreman-dev] Re: Plugins configuration managment platform

Hello the smart proxy chef plugin is only a proxy between Foreman - chef-client and Foreman - chef-server. Most of Foreman functionality proxies the communication through smart-proxy, the idea is that Foreman is running on one place e.g. in office while you need to talk to many hosts in

Re: [foreman-dev] Plugins configuration managment platform

If your devices provides REST API, you might have simple job templates (scripts to be executed) using curl and being run on smart proxies. See [1] for more details [1] https://www.theforeman.org/plugins/foreman_remote_execution/0.3/index.html -- Marek > > Le jeudi 29 juin 2017 13:09:53

Re: [foreman-dev] Plugins configuration managment platform

On středa 28. června 2017 11:34:00 CEST Fairouz el ouazi wrote: > Hi everyone , > > I'm a beginner in using foreman ,So before in take the adventure i > want to know if the fact that it exists a plugin for managing chef is there > any chance to develop a new one that will manage my own

Re: [foreman-dev] [Infra] Service accounts and secret storage

On pondělí 26. června 2017 14:31:32 CEST Greg Sutcliffe wrote: > Hey all, > > Continuing the theme of "reducing the bus factor", I want to talk about > the accounts we use for things like Rackspace, Scaleway, etc. > > Currently the rackspace account actually sends emails to a Red Hat > address -

Re: [foreman-dev] Re: Unit test jenkins job with all plugins enabled

While I agree, one thing that properly defined plugin DSL does not solve is the fact, that plugins now depend on each other. Few examples openscap, katello depends on remote execution katello, remote execution, ansible, chef, ... depends on foreman tasks remote execution depends on foreman

Re: [foreman-dev] Unit test jenkins job with all plugins enabled

On čtvrtek 1. června 2017 12:17:25 CEST Lukas Zapletal wrote: > Hello, > > I would like to open discussion about having a unit test job of > foreman with all major plugins enabled (katello, discovery, bootdisk, > rex, openscap). Some of the bugs we found in Discovery 9.0 would have > been found

Re: [foreman-dev] Re: [RFC] HTTP proxy for requests

Sorry for being late to the party, sending my 2c: I agree with having more complicated solution where users could have separate proxies per service is good long-term goal. AFAIK we don't the solution atm. Therefore I think introducing support for single, global proxy sounds as improvement

Re: [foreman-dev] [RFC] Proposal: make foreman STI to work even when an inherited class is not found in Ruby.

Thanks for bringing this up. I think the right approach is to have plugin uninstallation or rather clean up rake tasks. The clean up should IMHO delete all data that would case problems after code removal. It shouldn't try to revert the schema changes, but destroy all data that can cause

Re: [foreman-dev] Nominating Daniel Lobato for commiter to release related tasks

On úterý 25. dubna 2017 9:19:40 CEST Dominic Cleal wrote: > On 24/04/17 12:59, Marek Hulán wrote: > > based on our handbook [1]. I'd like to nominate Daniel for commit access > > to > > > > the following repositories: > > - foreman-infra > > - for

[foreman-dev] Nominating Daniel Lobato for commiter to release related tasks

Hello devs, based on our handbook [1]. I'd like to nominate Daniel for commit access to the following repositories: - foreman-infra - foreman-installer - foreman-packaging ( to branch and cherry-pick to the release branch ) Daniel contributes to the project for a long time, also in this

Re: [foreman-dev] omnibus packaging

Hello while it would made the packaging easier I don't think it's a very good approach. If there's some security issue found in one of deps, we'd need to build new version of the whole stack because of that. Btw on rpm based systems we use isolated ruby through software collection so it should

Re: [foreman-dev] Re: Revert removal of @host.params for host_param

On pondělí 17. dubna 2017 11:22:07 CEST Daniel Lobato wrote: > Sorry to relive the topic but > https://github.com/theforeman/foreman/pull/4219 didn't get in, > and it's time to update the documentation for 1.15 including deprecations. > > Since reverting the change is probably something not to be

Re: [foreman-dev] Unify date format in Foreman and plugins

On čtvrtek 13. dubna 2017 8:13:11 CEST Timo Goebel wrote: > Am 12.04.17 um 18:21 schrieb Ewoud Kohl van Wijngaarden: > > On Wed, Apr 12, 2017 at 06:02:34PM +0200, Marek Hulán wrote: > >> Thanks guys so far, I'm sending comments below in text that are also > >> r

Re: [foreman-dev] Unify date format in Foreman and plugins

On středa 12. dubna 2017 17:55:21 CEST Marek Hulán wrote: > On středa 12. dubna 2017 16:14:36 CEST Bryan Kearney wrote: > > +1 on the format > > > > To make sure I am clear: > > > > 1) Dates will be stored in the DB as UTC. > > yes, but should not mat

Re: [foreman-dev] Unify date format in Foreman and plugins

0PM +0200, Lukas Zapletal wrote: > > I like "ago" format with hover full date value. Thanks for putting > > effort in this! > > > > LZ > > > > On Wed, Apr 12, 2017 at 3:39 PM, Marek Hulán <mhu...@redhat.com> wrote: > > > Hello, > > >

Re: [foreman-dev] Unify date format in Foreman and plugins

your profile $username in top right corner -> My account see Timezone field which defaults to "Browser timezone" but can be set to any time zone -- Marek > > -- bk > > On 04/12/2017 09:39 AM, Marek Hulán wrote: > > Hello, > > > > I'd like to sugge

[foreman-dev] Unify date format in Foreman and plugins

Hello, I'd like to suggest one recommended way of displaying date/time information on all pages. We started a discussion in a PR [1] that would change the format for config reports, please take a look there for possible solutions. After a discussion with Roxanne (cc) on another page we agreed

Re: [foreman-dev] Organization titles in CLI

On úterý 11. dubna 2017 14:30:50 CEST Tomas Strachota wrote: > Thanks, i get it now. It's also viable solution. > One complication is that we would need to find a way how to deprecate > current usage of --parent in update commands and replace it with > --new-parent. But it's probably more

Re: [foreman-dev] Link to redmine issues using prprocessor

On pátek 7. dubna 2017 14:35:41 CEST John Mitsch wrote: > The greasmonkey script works great! Really helpful, thanks for sharing. For > those who are wondering (like I was), it requires the greasemonkey browser > plugin: > > https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/ or > >

Re: [foreman-dev] Dev/Design Weekly Meeting - Subscriptions

Hello Sean, I'm sorry if we created a feeling that we're doing something behind closed doors. Let me explain the background. When Roxanne started to look at the UI/UX improvements we quickly realized that Foreman with all its plugins is a big application and it seemed as too much to digest at

Re: [foreman-dev] No provisioning templates in dev foreman

Hello, You can run rake db:seed multiple times and it should always only seed missing data (non-destructive). If you want to be extra sure, just do the db backup beforehand. And yes, the file that you linked should create template kinds and templates. Hope this helps -- Marek On čtvrtek 9.

[foreman-dev] Form labels help icon change

Hello a PR [1] changing the form labels help icons was merged yesterday and will be part of upcoming 1.15 release. The change moved icons with popover help from right of the form field to the field label. If you're author of plugin that extends Foreman UI by fields with such help, you might

Re: [foreman-dev] Seeding templates overrides custom changes - should we lock templates we ship?

> But locking the templates we ship would be preferable to me. > > > - Stephen > > On Fri, Feb 17, 2017 at 9:04 AM, Marek Hulán <mhu...@redhat.com> wrote: > > Hello foreman-devs, > > > > recently I was told about the bug that we override all templates

Re: [foreman-dev] Re: Seeding templates overrides custom changes - should we lock templates we ship?

t; > > > - Timo > > > > > > [1] https://github.com/theforeman/foreman/pull/4283 > > > > > > Am Freitag, 17. Februar 2017 15:05:13 UTC+1 schrieb Marek Hulán: > > >> Hello foreman-devs, > > >> > > &g

Re: [foreman-dev] Opinions from plugin maintainers wanted: permissions and roles

Thaks for summary, just one quick comment where I think it needs clarification On středa 25. ledna 2017 13:59:57 CET Lukas Zapletal wrote: > Corrections. > > > Why you don't like explicit lock actions? > > I misinterpreted your statements above, looks like we both like > explicit locking. > >

Re: [foreman-dev] Opinions from plugin maintainers wanted: permissions and roles

On pondělí 23. ledna 2017 17:07:30 CET Lukas Zapletal wrote: > > If you're concerned about the permissions table, this does not help. > > Permission are created there by plugin. If the permission is removed > > later, it should be removed from all roles anyway, user could already > > assign it to

Re: [foreman-dev] Opinions from plugin maintainers wanted: permissions and roles

On úterý 24. ledna 2017 0:02:15 CET Ivan Necas wrote: > Lukas Zapletal writes: > >> If you're concerned about the permissions table, this does not help. > >> Permission are created there by plugin. If the permission is removed > >> later, it should be removed from all roles

Re: [foreman-dev] Opinions from plugin maintainers wanted: permissions and roles

Thanks for update, sending few more comments below in text On pondělí 23. ledna 2017 12:48:46 CET Lukas Zapletal wrote: > > Sorry I don't get it, especially the price. What's the difference between > > core and plugins in terms of permissions upgrades? If you rename plugin > > permission you need

Re: [foreman-dev] Moving foreman-tasks to the core: the plan

On pátek 20. ledna 2017 2:51:06 CET Ewoud Kohl van Wijngaarden wrote: > On Thu, Jan 19, 2017 at 06:04:58PM +0100, Ivan Necas wrote: > > Lukas Zapletal writes: > > >> I'm not sure I follow what you mean by administrative tasks. Note that > > >> reports > > >> import and puppet

Re: [foreman-dev] Opinions from plugin maintainers wanted: permissions and roles

On úterý 17. ledna 2017 14:45:53 CET Ondrej Prazak wrote: > On Tue, Jan 17, 2017 at 12:08 PM, Tomas Strachota > > wrote: > > On Mon, Jan 16, 2017 at 6:55 PM, oprazak wrote: > > > Hi, > > > I recently started identifying problematic areas in Permissions

Re: [foreman-dev] Opinions from plugin maintainers wanted: permissions and roles

On úterý 17. ledna 2017 15:46:56 CET Lukas Zapletal wrote: > On Mon, Jan 16, 2017 at 6:55 PM, oprazak wrote: > > So if a plugin is installed, user has to go and find what role/permission > > is missing or ask someone who can grant permissions. > > I do not think the proposed

Re: [foreman-dev] New community-templates structure

On čtvrtek 8. prosince 2016 16:58:24 CET Greg Sutcliffe wrote: > Oh, another thought, possibly half-baked - is there any impact on backwards > compatibility? IIRC foreman_templates doesn't actually care about the > directory structure (it's a **/*erb glob) but perhaps I've overlooked > something?

Re: [foreman-dev] Revert removal of @host.params for host_param

Hello The discussion has diverged into something different. People agree we should add an extra layer but implemented through proxy objects. It's also clear no one starts actively working on this right now. At the same time I want to add new macro, let's say rpm_distro? which returns

Re: [foreman-dev] Community template repository labels

Hello, labels might help so +1 for that. I plan to send a PR with new directory structure as discussed at [1] soon. It might help the bot to just check the directories of touched files. [1] https://groups.google.com/forum/#!topic/foreman-dev/bzfBWEtIMpg -- Marek On pátek 13. ledna 2017

Re: [foreman-dev] Revert removal of @host.params for host_param

On čtvrtek 12. ledna 2017 9:32:06 CET Stephen Benjamin wrote: > - Original Message - > > > From: "Marek Hulán" <mhu...@redhat.com> > > To: foreman-dev@googlegroups.com > > Sent: Thursday, January 12, 2017 2:59:39 AM > > Subject: Re

Re: [foreman-dev] Revert removal of @host.params for host_param

> Also, the deprecation wasn't really smooth as it broke REX tests. > http://ci.theforeman.org/job/test_plugin_matrix/2466/ One more note, REX was not broken by this, users were no affected. It's just the test that checks "no warning was reported". The test tests something more than it

Re: [foreman-dev] Revert removal of @host.params for host_param

On středa 11. ledna 2017 14:22:53 CET Stephen Benjamin wrote: > - Original Message - > > > From: "Daniel Lobato Garcia" > > To: foreman-dev@googlegroups.com > > Sent: Wednesday, January 11, 2017 11:05:39 AM > > Subject: [foreman-dev] Revert removal of @host.params

Re: [foreman-dev] HoundCI - annoying?

Hello, yes, I find it annoying and I liked the jenkins job more. It would be great if hound would be able to use reviews that would generate one email per review. Hopefully they work on it. Otherwise I'd be for moving back to jenkins. On středa 11. ledna 2017 12:07:38 CET David Davis wrote: >

Re: [foreman-dev] Moving foreman-tasks to the core: the plan

Few comments below On čtvrtek 5. ledna 2017 15:25:47 CET Lukas Zapletal wrote: > Is it only the Rails App that depends on Foreman Core? What's reasonable > plan to me is: > > a) Extract core part that does not depend on Foreman core into a simple gem > (that's what you propose I guess) and make

Re: [foreman-dev] Moving foreman-tasks to the core: the plan

+1 -- Marek On středa 4. ledna 2017 10:29:19 CET Ivan Necas wrote: > Hello friends, > > You've might noticed we started using foreman-tasks inside the > foreman-core since [1] was merged. Unfortunately, we hit issues in the > packaging phase and the proposed workarounds were not accepted ([2] >

Re: [foreman-dev] Example of how to extend the hostgroups action menu

On středa 21. prosince 2016 13:37:12 CET Daniel Kuffner wrote: > Hi All, > > Do we have somewhere an example of how to extend the hostgroups action menu > item via foreman plugin? Is that possible? > > thank you, > Daniel Hello, I can't find any example for extending menu actions, but it

Re: [foreman-dev] Simple Example for foreman-tasks locks

On pátek 16. prosince 2016 16:28:47 CET Daniel Kuffner wrote: > Hi All, > > I was looking for a simple example of how to use locks of foreman-tasks > (dynflow). I can see that Actions::EntryAction mixes in the > Actions::Helpers::Lock but for me it is not clear how to use it. > > regards, >

Re: [foreman-dev] Use mention-bot to increase reviews?

On úterý 6. prosince 2016 12:37:23 CET Daniel Lobato Garcia wrote: > On 12/06, Sean O'Keeffe wrote: > > Hows this going for everybody? I personally quite like it > > Personally it's just noise for me, but if it works for some people it > causes no harm +1, I'm failing to get time for reviews and

Re: [foreman-dev] Way to create new foreman user using rake ?

Hello I don't think so, but you can easily create admin using API or hammer CLI. Hope this helps -- Marek On čtvrtek 1. prosince 2016 2:42:03 CET myrubycodecco...@gmail.com wrote: > Hi all, > > As we can rake permissions:reset etc, is there a way to create another > admin user via rake also? >

Re: [foreman-dev] Using certificates for SSH access

Hello some comments below On Tuesday 13 of September 2016 08:51:12 Ohad Levy wrote: > Hi, > > I was looking at [1] which talks about how to leverage a CA for managing > SSH access, and I thought it could be interesting for REX and potentially > for foreman to manage. > > In the post, they

Re: [foreman-dev] Hash rocket syntax

rek > I think there’s probably a happy medium between not using rubocop and > enabling all rubocop cops. > > > David > > On Tue, Aug 23, 2016 at 11:22 AM, Marek Hulán <mhu...@redhat.com> wrote: > > On Tuesday 23 of August 2016 07:47:31 David Davis wrote: >

Re: [foreman-dev] Hash rocket syntax

great way to learn good Ruby coding > standards. > > That said, I agree it would be nice to get opinions of community members > who contribute to foreman and their experiences with rubocop. > > [1] https://github.com/bbatsov/ruby-style-guide > > > David > > On Tue

Re: [foreman-dev] Possible Feature Requst: Discussion: EC2 Subnet Display - include comment/description field in seperate view

On Tuesday 09 of August 2016 08:22:38 Matt Darcy wrote: > I've been doing a little bit of POC work on foreman 1.11 with EC2 (not > bothered moving to 1.12 for this POC as it's not really version specific). > > when building/modifying a host the EC2 compute plugin pulls a list of > subnets

Re: [foreman-dev] No uploader

etwork','cpu'] > foreman_facts_blacklist ['kernel','counters','interfaces::sit0'] > foreman_cache_file '/var/cache/chef_foreman_cache.md5' > foreman_reports_upload true > reports_log_level "notice" > > On Wednesday, August 3, 2016 at 1:05:36 AM UTC-7, Marek Hul

Re: [foreman-dev] List moderation "always allow posts" errors

On Thursday 04 of August 2016 13:33:32 Dominic Cleal wrote: > Are any other list moderators (of either -dev or -users) getting the > following errors when allowing the current plus future posts from a user? > > "One message has been posted. Failed to always allow posts from > u...@example.com due

Re: [foreman-dev] No uploader

Hello, how did you install the handler? You have to modify /etc/chef/client.rb to register it. See [1] for example how to do it [1] https://github.com/theforeman/chef-handler-foreman#installation On Tuesday 02 of August 2016 11:46:40 Thomas Fee wrote: > Trying to get chef-handler-foreman to

Re: [foreman-dev] Plugin Proposal: User-defined ENC mutation

Hello thanks for the write up. first of all - I find it useful. Not only for users but for plugin developers too. I encountered this scenario several times already, I'd like to extend ENC from plugin. For example in foreman_openscap we provide puppet module to configure scap client and we

Re: [foreman-dev] Deprecate EL6?

On Thursday 28 of July 2016 16:34:30 Greg Sutcliffe wrote: > So I had a read back through the thread, and drew a few conclusions. The > history seems to be: > > * The thread was opened ~10 weeks ago, and went quiet ~6 weeks ago > * At that time, there were 5 upvotes (Dominic, Daniel, Ewoud,

Re: [foreman-dev] "Team AL-GTD - 1" deleted

On Wednesday 27 of July 2016 09:09:20 Dominic Cleal wrote: > On 27/07/16 08:54, Marek Hulán wrote: > > On Monday 25 of July 2016 07:57:35 Dominic Cleal wrote: > >> I've deleted the the "Team AL-GTD - 1" version that somebody had added > >> to the Foreman pro

Re: [foreman-dev] Re: external_node_v2 refactor!

Hello I don't think there's too much functionality in this script. Maybe a unit test for what's worth of testing would be enough? In such case I'd recommend using minitest. It has some stubbing built-in but maybe webmock [1] might be useful for stubbing out communication with Foreman. [1]

Re: [foreman-dev] hammer_cli_foreman_openscap

Hello I have few more findings with the latest version, please find them below in text. Some of them might need fixing in API rather than here. Feel free to just create redmine issue from them in such case. Once below comments are fixed I think we can move it under theforeman org (unless