Thank you Daniel!
We'll try this out when all of our code is ready, and will report back here
with any issues we hit etc in case somebody else comes across this thread.
Looks like this should work in a sandbox experiment.
On Wednesday, 29 November 2017 08:54:56 UTC, Daniel Lobato wrote:
>
> On
On 11/28, 'Tom Farrow' via Foreman users wrote:
> Thank you Daniel, this does indeed look like our best approach.
>
> A concern I do have is with "search_for". We also have an apache_activemq
> module, and it is important that this is not affected by the query. Is
> there a way to specify the searc
Thank you Daniel, this does indeed look like our best approach.
A concern I do have is with "search_for". We also have an apache_activemq
module, and it is important that this is not affected by the query. Is
there a way to specify the search using regex?
On Monday, 27 November 2017 14:47:16 UT
On 11/27, 'Tom Farrow' via Foreman users wrote:
> Hi,
>
> We'd like to rename a couple of classes, retaining all parameter overrides
> etc.
>
> We're looking to move "::apache" to "::legacy_apache" including all other
> classes within the module (::apache::mod::python etc).
>
> To me, the workflow
Hi,
We'd like to rename a couple of classes, retaining all parameter overrides
etc.
We're looking to move "::apache" to "::legacy_apache" including all other
classes within the module (::apache::mod::python etc).
To me, the workflow seems to be:
- Change code to use the new name
- In the Forem
