On Thu, Sep 8, 2016 at 5:56 AM, Akila Ravihansa Perera <[email protected]> wrote:
> Hi Imesh, > > On Thu, Sep 8, 2016 at 3:47 AM, Imesh Gunaratne <[email protected]> wrote: > >> What would be the reason for using rsync in the Vagrant setup [2]? Do we >> update files inside the VM? >> >> [2] https://github.com/wso2/puppet-common/blob/56b34c4c2db11f07d >> ca739f0e92bf1d955cfcb46/vagrant/Vagrantfile#L53 >> > > We ran into an issue when mounting Hieradata folder (which is a symlink > now) to the VM. It seems Vagrant does not fully support mounting symlinks > so we had to rsync it. > I talked to Anuruddha on this. This is what has happened in ESB module: - The setup.sh bash script has tried to create symlinks to hieradata folders from product puppet module and those have failed. - However the bash script has not detected that and continued rest of the logic. - As a result of this, file synchronization in Vagrant has failed with the above error. IMO if a such error occurs in setup.sh, it should stop at that point and raise an error. @Akila: I don't think using rsync as a workaround for some other problem is a good solution. If the root cause of the issue is with symlinks better to fix that. [3] https://www.vagrantup.com/docs/synced-folders/rsync.html Thanks > Thanks. > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > -- *Imesh Gunaratne* Software Architect WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: https://medium.com/@imesh TW: @imesh lean. enterprise. middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
