You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/05/02 20:49:05 UTC
[jira] [Updated] (AURORA-1204) Symlink upstart configurations
instead of copying them
[ https://issues.apache.org/jira/browse/AURORA-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Farner updated AURORA-1204:
--------------------------------
Story Points: 2
> Symlink upstart configurations instead of copying them
> ------------------------------------------------------
>
> Key: AURORA-1204
> URL: https://issues.apache.org/jira/browse/AURORA-1204
> Project: Aurora
> Issue Type: Story
> Components: Testing
> Reporter: Bill Farner
> Assignee: Bill Farner
>
> In the vagrant environment, we perform a step where we copy the upstart configurations to /etc/init \[1\]. The way this is done makes it challenging to change the upstart configurations later, the easiest way being to destroy and re-create the environment. Consider symlinking these files instead, so that their definitions are updated by rsync along with other code.
> \[1\] https://github.com/apache/incubator-aurora/blob/ad211da2f2490722a10cce95a2bb4fb55fd1c16f/examples/vagrant/provision-dev-cluster.sh#L60-L61
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)