You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A little bit of background: we use a very old forked version of r10k which did not have local module support at the time.
It was implement in our fork (along with some other patches) and a local module would look like this in Puppetfile:
mod 'my_module', :local
Later on, it was implemented in the upstream version, but the syntax is a little different:
mod 'my_module', local: true
# or (essentially the same thing, but with older Ruby syntax)
mod 'my_module', :local => true
At this point, this gem only recognized the first version and also writes Puppetfiles in that format.
I believe the best way to move forward is to first start supporting both formats while reading, but keep on writing Puppetfile in the old format.
Then release a major version that will start writing Puppetfile in a new format (and maybe the old format as a toggle feature).
The text was updated successfully, but these errors were encountered:
A little bit of background: we use a very old forked version of
r10k
which did not have local module support at the time.It was implement in our fork (along with some other patches) and a local module would look like this in Puppetfile:
Later on, it was implemented in the upstream version, but the syntax is a little different:
At this point, this gem only recognized the first version and also writes Puppetfiles in that format.
I believe the best way to move forward is to first start supporting both formats while reading, but keep on writing Puppetfile in the old format.
Then release a major version that will start writing Puppetfile in a new format (and maybe the old format as a toggle feature).
The text was updated successfully, but these errors were encountered: