Bolt 1.8.0 now available

[Puppet Product Updates]

Greetings!

We're happy to announce the release of Bolt 1.8.0. Highlights in this release include:

• Standard library functions

For more information, check out the release notes: 

https://puppet.com/docs/bolt/1.x/bolt_release_notes.html

To try this version of Bolt, follow the installation instructions for your operating system:

https://puppet.com/docs/bolt/1.x/bolt_installing.html

Thanks!

[vlastim...@gmail.com]

Hello,

On Friday, January 4, 2019 at 12:01:58 AM UTC+1, Puppet Product Updates wrote:

Greetings!

We're happy to announce the release of Bolt 1.8.0. Highlights in this release include:

• Standard library functions

how to uses those new functions?

I'm having following simple plan:

plan profiles::test {

  ctrl::sleep(5)

}

But, Bolt complains about unknown function:

$ bolt --boltdir=$PWD plan run profiles::test

Starting: plan profiles::test

Finished: plan profiles::test in 0.02 sec

{

  "kind": "bolt/pal-error",

  "msg": "Evaluation Error: Unknown function: 'ctrl::sleep'. (file: ...bolt/site/profiles/plans/test.pp, line: 2, column: 3)",

  "details": {

  }

}

I have Bolt 1.8.0 packaged for the C7:

$ rpm -q puppet-bolt

puppet-bolt-1.8.0-1.el7.x86_64

Thank you,

Vlastimil Holer

[Michael Smith]

Oof, we messed up packaging it. I’ll see about getting a new release out today.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/819d7517-f412-498b-b1c4-a7b7cc66639c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Eric Sorenson]

Vlastimil - I'm forwarding this message to the puppet-users list instead of puppet-announce.

--eric0

From: vlastim...@gmail.com

Subject: Re: Bolt 1.8.0 now available

Date: January 4, 2019 at 3:46:31 AM PST

To: Puppet Announce <puppet-...@googlegroups.com>

Hello,

On Friday, January 4, 2019 at 12:01:51 AM UTC+1, Puppet Product Updates wrote:

Greetings!

We're happy to announce the release of Bolt 1.8.0. Highlights in this release include:

• Standard library functions

how to use those new functions?

Having a following simple plan:

plan profiles::test {

  ctrl::sleep(5)

}

Complains about unknown function:

$ bolt --boltdir=$PWD plan run profiles::test

Starting: plan profiles::test

Finished: plan profiles::test in 0.02 sec

{

  "kind": "bolt/pal-error",

  "msg": "Evaluation Error: Unknown function: 'ctrl::sleep'. (file: .../bolt/site/profiles/plans/test.pp, line: 2, column: 3)",

  "details": {

  }

}

Having Bolt 1.8 from packages for C7:

[vlastim...@gmail.com]

On Friday, January 4, 2019 at 5:28:29 PM UTC+1, Eric Sorenson wrote:

Vlastimil - I'm forwarding this message to the puppet-users list instead of puppet-announce.

Sorry, my fault. I have noticed the wrong group (since the announcements are the same in both) after I sent the question. Thanks!

[Russell Fulton]

Hi

I have not come across Bolt before and have been looking at the docs. It certainly looks like something that I can use. I am assuming that one installs Bolt on your puppet server? But it really isn’t clear from the docs which seem to assume you already have the “big picture” of how it fits in with puppet. The current doc assume a context I don’t have.

A couple of higher level paragraphs on the web page or the github README would be a great help.

Russell

[Alex Dreyer]

On Sat, Jan 5, 2019 at 6:04 PM Russell Fulton <russell...@gmail.com> wrote:

Hi

I have not come across Bolt before and have been looking at the docs.  It certainly looks like something that I can use.  I am assuming that one installs Bolt on your puppet server?   But it really isn’t clear from the docs which seem to assume you already have the “big picture” of how it fits in with puppet.  The current doc assume a context I don’t have.

Bolt is a standalone configuration management tool. If can be used with puppet infrastructure to handle orchestration across multiple nodes or ad hoc debugging/changes. It can also manage configuration on nodes that are not running the puppet agent or connected to a master. It's a command line tool with no long running service like puppet server so where you run it depends on your workflow. My general recommendation is to start with it installed on your workstation or laptop and later install it on a bastion or the puppet master only if you need to.

A couple of higher level paragraphs on the web page or the github README would be a great help.

I'll see where I can fit this in, thanks.

 

Russell

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6E33021E-596A-48B1-8B75-1CB816621D8A%40gmail.com.

[Russell Fulton]

Thanks Alex!

I have some messy execs to handle updating software from a bit bucket repository (amongst other things). I take it that would be a good candidate for Bolt.

> On 8/01/2019, at 6:03 AM, Alex Dreyer <al...@puppet.com> wrote:
>
>
>
> On Sat, Jan 5, 2019 at 6:04 PM Russell Fulton <russell...@gmail.com> wrote:
> Hi
>
> I have not come across Bolt before and have been looking at the docs. It certainly looks like something that I can use. I am assuming that one installs Bolt on your puppet server? But it really isn’t clear from the docs which seem to assume you already have the “big picture” of how it fits in with puppet. The current doc assume a context I don’t have.
>
> Bolt is a standalone configuration management tool. If can be used with puppet infrastructure to handle orchestration across multiple nodes or ad hoc debugging/changes. It can also manage configuration on nodes that are not running the puppet agent or connected to a master. It's a command line tool with no long running service like puppet server so where you run it depends on your workflow. My general recommendation is to start with it installed on your workstation or laptop and later install it on a bastion or the puppet master only if you need to.

So yo get things going independent of Puppet and then integrate it. Sounds sensible. I am trying hard to get all the configuration stuff in just one place to make it easier for others to maintain so ultimately I want to drive it all out of heira data which is generated by a ruby script from a bunch of json files. The system is a multi sensor IDS system running Suricata and Moloch (and the associated Elasticsearch machines).

I am using the organisation (major university) puppet server which I have no direct access to and one (horribly bloated) module that gets loaded for my machines. We really should have the enterprise version but costs more that folk are prepared to pay. Such is life ;)

>
> A couple of higher level paragraphs on the web page or the github README would be a great help.
>
> I'll see where I can fit this in, thanks.
>
>
> Russell
>
> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6E33021E-596A-48B1-8B75-1CB816621D8A%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMahoJsaCwg8D_LSgQT9ceAb6jvjSEtV_iN-Yqtf_A56_RQYaQ%40mail.gmail.com.