Fair enough. It's good to know just in case something can be done.
In this case, I don't think there's much of a choice.
However, if it is a competing product, I don't think that the PuppetDB
project would reject a PR for support for your internal project. It might
be faster than getting
Agreed: it's a service, you won't be playing with the Postgres nerd knobs
very much, if at all.
On Sun, Dec 18, 2016 at 2:46 PM Jo Rhett wrote:
> Consider listing PuppetDB as a single application, not as an app and
> database. Closed box, vendor integrated data
Consider listing PuppetDB as a single application, not as an app and
database. Closed box, vendor integrated data management.
On Fri, Dec 16, 2016 at 2:52 PM, Johnson Earls
wrote:
> Hello all,
>
> I was just wondering - has anyone come across a plugin or something that
>
Trevor: PostgreSQL is considered a competing product. We're not allowed to
use competing products without getting approval from the corporate
information security group, legal, marketing, and a high level corporate
officer (I don't remember how high off the top of my head, but at least 4
Hi Johnson,
Do you have any information on why PostgreSQL is taboo? It might help to
justify supporting additional back-end databases.
To solve your exported resources problem, you can use this as an example
Sorry, but no. I'm quite sure that PuppetDB (and Postgres) is a hard
dependency for exported resources.
--
Lowe Schmidt | +46 723 867 157
On 16 December 2016 at 23:52, Johnson Earls wrote:
> Hello all,
>
> I was just wondering - has anyone come across a plugin or
Hello all,
I was just wondering - has anyone come across a plugin or something that
would allow the use of exported resources in Puppet 4.x *without* using
PuppetDB? The company I work for has declared PostgreSQL taboo within the
corporate network and so I cannot run PuppetDB, and the lack of