Agree with Anthony. A copy command would either duplicate what deploy does by only putting files within as specific location in the server's directory or creating a security nightmare if allowed to write anywhere on the host.
On Fri, Jan 6, 2017 at 7:56 AM Anthony Baker <aba...@pivotal.io> wrote: > I think there are lots of great OS orchestration and automation tools. > I’m not sure I understand the need for `gfsh cp`. If I could easily grab > the member hostnames from `gfsh list members` and pipe them into mpssh (for > example) that would do the job. > > I *do* like the idea of an improved `gfsh deploy` that supports hot deploy > and reconfiguration. > > Anthony > > > On Jan 6, 2017, at 2:38 AM, Swapnil Bawaskar <sbawas...@pivotal.io> > wrote: > > > > Some application may need to copy files to all the servers. These files > > could either be data files or they could be configuration files needed by > > the application or they could be jar files (that don't have functions but > > have say, spring data geode jar files) that need to be on the server's > > classpath. > > We could accomplish this by enhancing the current gfsh "deploy" command > to > > accept any kind of file and write it to the servers file system OR > create a > > new gfsh "copy" command to copy any arbitrary file to the servers. > > I would personally like to repurpose the deploy command but would like to > > hear the community's opinion. > > > > Thanks! > >
