<commit_before>Feature: paasta-deployd deploys apps

  Scenario: deployd will deploy a new app
    Given a working paasta cluster
      And paasta-deployd is running
      And I have yelpsoa-configs for the marathon job "test-service.main"
      And we have a deployments.json for the service "test-service" with enabled instance "main"
     Then we should see "test-service.main" listed in marathon after 60 seconds
     Then we can run get_app
     Then paasta-deployd can be stopped

  Scenario: deployd will re-deploy an app if its marathon-*.yaml changes
    Given a working paasta cluster
      And paasta-deployd is running
      And I have yelpsoa-configs for the marathon job "test-service.main"
      And we have a deployments.json for the service "test-service" with enabled instance "main"
     Then we should see "test-service.main" listed in marathon after 60 seconds
     Then we can run get_app
     Then we set a new command for our service instance to "/bin/bash -c 'echo deploy-all-the-things'"
    Given I have yelpsoa-configs for the marathon job "test-service.main"
     Then the appid for "test-service.main" should have changed
     Then we should not see the old version listed in marathon after 60 seconds
     Then we should see "test-service.main" listed in marathon after 60 seconds
     Then we can run get_app
     Then paasta-deployd can be stopped

  Scenario: deployd will re-deploy an app if its deployment.json is updated
    Given a working paasta cluster
      And paasta-deployd is running
      And I have yelpsoa-configs for the marathon job "test-service.main"
      And we have a deployments.json for the service "test-service" with enabled instance "main"
     Then we should see "test-service.main" listed in marathon after 30 seconds
     Then we can run get_app
    Given we have a deployments.json for the service "test-service" with enabled instance "main" image "test-image-foobar1"
     Then the appid for "test-service.main" should have changed
     Then we should not see the old version listed in marathon after 60 seconds
     Then we should see "test-service.main" listed in marathon after 60 seconds
     Then we can run get_app
     Then paasta-deployd can be stopped

  Scenario: deployd starts and only one leader
    Given a working paasta cluster
      And paasta-deployd is running
     Then a second deployd does not become leader
     Then paasta-deployd can be stopped
     Then a second deployd becomes leader
<commit_msg>Skip deployd tests for now<commit_after>Feature: paasta-deployd deploys apps

  @skip
  Scenario: deployd will deploy a new app
    Given a working paasta cluster
      And paasta-deployd is running
      And I have yelpsoa-configs for the marathon job "test-service.main"
      And we have a deployments.json for the service "test-service" with enabled instance "main"
     Then we should see "test-service.main" listed in marathon after 60 seconds
     Then we can run get_app
     Then paasta-deployd can be stopped

  @skip
  Scenario: deployd will re-deploy an app if its marathon-*.yaml changes
    Given a working paasta cluster
      And paasta-deployd is running
      And I have yelpsoa-configs for the marathon job "test-service.main"
      And we have a deployments.json for the service "test-service" with enabled instance "main"
     Then we should see "test-service.main" listed in marathon after 60 seconds
     Then we can run get_app
     Then we set a new command for our service instance to "/bin/bash -c 'echo deploy-all-the-things'"
    Given I have yelpsoa-configs for the marathon job "test-service.main"
     Then the appid for "test-service.main" should have changed
     Then we should not see the old version listed in marathon after 60 seconds
     Then we should see "test-service.main" listed in marathon after 60 seconds
     Then we can run get_app
     Then paasta-deployd can be stopped

  @skip
  Scenario: deployd will re-deploy an app if its deployment.json is updated
    Given a working paasta cluster
      And paasta-deployd is running
      And I have yelpsoa-configs for the marathon job "test-service.main"
      And we have a deployments.json for the service "test-service" with enabled instance "main"
     Then we should see "test-service.main" listed in marathon after 30 seconds
     Then we can run get_app
    Given we have a deployments.json for the service "test-service" with enabled instance "main" image "test-image-foobar1"
     Then the appid for "test-service.main" should have changed
     Then we should not see the old version listed in marathon after 60 seconds
     Then we should see "test-service.main" listed in marathon after 60 seconds
     Then we can run get_app
     Then paasta-deployd can be stopped

  @skip
  Scenario: deployd starts and only one leader
    Given a working paasta cluster
      And paasta-deployd is running
     Then a second deployd does not become leader
     Then paasta-deployd can be stopped
     Then a second deployd becomes leader

{'fraction_non_alphanumeric': 0.04419669520207047, 'fraction_numerical': 0.005972526378658172, 'mean_word_length': 3.1623860811930404, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5145229', 'n_tokens_mistral': 1424, 'n_tokens_neox': 1325, 'n_words': 684}