You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/30 23:05:12 UTC

[jira] [Commented] (METRON-91) Vagrant deploy: expose tags and skip_tags

    [ https://issues.apache.org/jira/browse/METRON-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265489#comment-15265489 ] 

ASF GitHub Bot commented on METRON-91:
--------------------------------------

Github user dlyle65535 commented on the pull request:

    https://github.com/apache/incubator-metron/pull/96#issuecomment-215995469
  
    Upon further review- I think I have something working that doesn't need the extra '--'.
    
    What would you guys think of the following?
    
    - Remove the singlenode-vagrant stuff from this PR
    - I'll push what I've been able to work up for that under METRON-91 (unless @merrimanr has sorted it, then he can)
    - For @merrimanr 's concern about pre-built dev images, let's see what it would take to make something like that vagrant upable (I think it's just adding a push provider to the Vagrantfile and setting up an Atlas account) so whatever we do will work with all singlenode dev-type images 
      



> Vagrant deploy: expose tags and skip_tags
> -----------------------------------------
>
>                 Key: METRON-91
>                 URL: https://issues.apache.org/jira/browse/METRON-91
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: David M. Lyle
>              Labels: deployment, newbie++
>
> Currently to use ansible.tags or ansible.skip_tags one has to edit the Vagrantfile. Expose this via environmental variables.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)