jimbodragon_acceptance_test 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: 788d3bdde1637420a6ea2fcb6748411b1a391e0645d0075fd3013233ccd30c48
4
+ data.tar.gz: 8612e4a250d5e2ea2a3bd8c0b6b6f2eacdc7cb89e175b17d5110f9e410c93525
5
+ SHA512:
6
+ metadata.gz: 18e583c3bc7c458642fd2b3172526fbb88857f800716f9d2f0f5c9be4c707d5f68f6fc3df33d9416d4b39fb4b0ad305a455e2b8748f453469e6b1c292bdc9a3c
7
+ data.tar.gz: ff109d7bb57cbf83bda0653b5b580ebaab06cb075fb6a91846bb69af45b392fd97c9e1171c158652e234b391565a56185a0996500e9a5686ef7d413302c27d83
checksums.yaml.gz.sig ADDED
Binary file
data/LICENSE ADDED
@@ -0,0 +1,5 @@
1
+ Copyright 2022 JimboDragon
2
+
3
+ All rights reserved, do not redistribute.
4
+
5
+ Jimmy Provencher
data/README.md ADDED
@@ -0,0 +1,96 @@
1
+ # ./
2
+
3
+ Brief description of ./
4
+
5
+ ## Maintainers
6
+
7
+ Names of core plans maintainers (The Habitat Maintainers humans@habitat.sh is usually sufficient)
8
+
9
+ ## Type of Package
10
+
11
+ This should state whether the package is a service package or a binary package.
12
+
13
+ A service package is something that will be run by the Habitat supervisor (i.e. core/postgresql). A service package must always have a run file or define pkg_svc_run in the plan.sh file.
14
+
15
+ A binary package is something that packages up a standalone binary, something that does not need to run under the Habitat supervisor (i.e. core/dep). They are often used as dependencies of other packages. Binary packages do not have a run file and do not need to define pkg_svc_run in the plan.sh file.
16
+
17
+ ## Usage
18
+
19
+ How would a user use this package? i.e. can a user simply call the package as a dependency of their application? Or is there more they need to do?
20
+
21
+ ## Bindings
22
+
23
+ *(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
24
+
25
+ How do other services that want to consume this service bind to it?
26
+
27
+ Checkout [the core/postgresql](https://github.com/habitat-sh/core-plans/tree/master/postgresql) README for a good example of this.
28
+
29
+ ## Topologies
30
+
31
+ *(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
32
+
33
+ What topologies does this plan support?
34
+
35
+ ### Standalone
36
+
37
+ *(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
38
+
39
+ Check out [the Habitat docs on standalone](https://www.habitat.sh/docs/using-habitat/#standalone) for more details on what the standalone topology is and what it does.
40
+
41
+ If this plan can be used with the standalone topology, how do you do it?
42
+
43
+ Checkout [the core/postgresql](https://github.com/habitat-sh/core-plans/tree/master/postgresql) README for a good example of this.
44
+
45
+ ### Leader-Follower
46
+
47
+ *(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
48
+
49
+ If this plan can be used with the leader/follower topology, how do you do it?
50
+
51
+ Check out [the Habitat docs on Leader-Follower](https://www.habitat.sh/docs/using-habitat/#leader-follower-topology) for more details on what the leader-follower topology is and what it does.
52
+
53
+ Checkout [the core/postgresql](https://github.com/habitat-sh/core-plans/tree/master/postgresql) README for a good example of this (look under the Clustering heading)
54
+
55
+ ## Update Strategies
56
+
57
+ *(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
58
+
59
+ What update strategies would work best for this plan?
60
+
61
+ Checkout [the update strategy documentation](https://www.habitat.sh/docs/using-habitat/#update-strategy) for information on the strategies Habitat supports.
62
+
63
+ ### Configuration Updates
64
+
65
+ *(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
66
+
67
+ Checkout the [configuration update](https://www.habitat.sh/docs/using-habitat/#configuration-updates) documentation for more information on what configuration updates are and how they are executed.
68
+
69
+ Link to the plan's default.toml file to list all the configurable values of the plan.
70
+
71
+ If your plan has configuration values that require a complete rebuild when updated, note those here.
72
+
73
+ ## Scaling
74
+ *(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
75
+
76
+ (Optional, but recommended)
77
+
78
+ How would a user scale this service?
79
+
80
+ Can this service be run in a cluster and/or as high availability?
81
+
82
+ ## Monitoring
83
+
84
+ *(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
85
+
86
+ (Optional, but recommended)
87
+
88
+ How would a user monitor the health of this surface at the application layer?
89
+
90
+ This is separate from information about Habitat's HTTP API monitoring service. This section should include some suggestions about how someone could monitor the application or service outside of Habitat - i.e. using something like sumologic, logstash, etc. It does not need to be prescriptive, but should include some suggestions of where someone might start.
91
+
92
+ ## Notes
93
+
94
+ (Optional)
95
+
96
+ Anything that does not fit in the above sections should go here - i.e. how does this fit into a user's development workflow?
@@ -0,0 +1,46 @@
1
+ #!/opt/chef-workstation/embedded/bin/ruby
2
+ # Trap interrupts to quit cleanly. See
3
+ # https://twitter.com/mitchellh/status/283014103189053442
4
+ Signal.trap('INT') { exit 1 }
5
+ module JimboDragon
6
+ module AcceptanceTests
7
+ module StartCucumber
8
+ def self.start
9
+ extend JimboDragon::AcceptanceTests::StartCucumber
10
+ start_project
11
+ end
12
+
13
+ def install_chef
14
+ system('curl -L https://omnitruck.chef.io/install.sh | sudo bash -s -- -s once -P chef-workstation')
15
+ end
16
+
17
+ def install_cucumber
18
+ system('chef gem install cucumber')
19
+ end
20
+
21
+ def run_project()
22
+ system('chef exec cucumber')
23
+ end
24
+
25
+ def prepare_project(project_name)
26
+ install_chef
27
+ install_cucumber
28
+ end
29
+
30
+ def finalize_project()
31
+ system('knife node show $(hostname) -z')
32
+ end
33
+
34
+ def start_project(project_name)
35
+ current_file=__FILE__
36
+ current_parameter=ARGV
37
+ echo "Running project $project_name"
38
+ prepare_project project_name
39
+ run_project project_name
40
+ finalize_project
41
+ end
42
+ end
43
+ end
44
+ end
45
+
46
+ JimboDragon::AcceptanceTests::StartCucumber.start
data.tar.gz.sig ADDED
@@ -0,0 +1,4 @@
1
+ 8t�D�b�y�%�. ]����4?-Ȧ
2
+ �s`�L-?,
3
+ ħ���
4
+ �Þ^�|�ߍ�ķNH�%�P���_�}ښv���؞_��T�X�����R)��#�U��k!~0�F2��~ ]\����I�"�^�'�0 �3��0�x��\���
metadata ADDED
@@ -0,0 +1,123 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: jimbodragon_acceptance_test
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.1.1
5
+ platform: ruby
6
+ authors:
7
+ - Jimmy Provencher
8
+ autorequire:
9
+ bindir: bin
10
+ cert_chain:
11
+ - |
12
+ -----BEGIN CERTIFICATE-----
13
+ MIIEXjCCAsagAwIBAgIBATANBgkqhkiG9w0BAQsFADAsMSowKAYDVQQDDCFqaW1t
14
+ eS5wcm92ZW5jaGVyL0RDPWhvdG1haWwvREM9Y2EwHhcNMjIxMDE4MjExMjAwWhcN
15
+ MjMxMDE4MjExMjAwWjAsMSowKAYDVQQDDCFqaW1teS5wcm92ZW5jaGVyL0RDPWhv
16
+ dG1haWwvREM9Y2EwggGiMA0GCSqGSIb3DQEBAQUAA4IBjwAwggGKAoIBgQCex0r1
17
+ ngWBVriaiIpaW08qeFeaCMqRlotYWvXA4M796ahhyE0HUAz8IfqXyZL9FU3lyOW2
18
+ AdtO8ISR0W1nwOn3hJj6KL+KDylHP0Ih3k7pI7NysaBxi3QlpWSVOw+DOJA2OsLm
19
+ W/a9ZTeRigHiLkq4ZGIYiJFw7LhZSC1onXkGXu7vjST0ZFGL75z7kg+7zVRdB8IB
20
+ LwfwU93VPlRdNSBu4D3te0A6jN+Gvh2zvAKqd5muxT2869R0AaSDDeXyn70CbQry
21
+ AgXwO62Zl0whs5SYKZT4SHTsKPPEvIaj9UXJ863/lvxUQaqvpl+w+I/JvWaBcUS5
22
+ Ym+11VgydPyPZUiJN9EsvJJw9SuxjOXFtoGBVJ5SC3bgHeN6n74c8TCoH0IzZYlE
23
+ NLdQLw673cC4PkU2TRLYd9hKkH/0br/uxFiIcKjb0NfGERjZhYNugYNPCUzeYiM7
24
+ s4azT0a9oAbTVDjObG6M1xwOstnrdJtRaYDCswjVVtusAI10kNj4pvLVndECAwEA
25
+ AaOBijCBhzAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHQ4EFgQUXwYB8v7w
26
+ YzFbhswW02omiSMDHBAwJgYDVR0RBB8wHYEbamltbXkucHJvdmVuY2hlckBob3Rt
27
+ YWlsLmNhMCYGA1UdEgQfMB2BG2ppbW15LnByb3ZlbmNoZXJAaG90bWFpbC5jYTAN
28
+ BgkqhkiG9w0BAQsFAAOCAYEAecUO+U9BJ90Lz75iwpvmHjAy8CixyATIEb1iw/t2
29
+ tKa/XYQN8gRvYPIESWI0cgeakOZjQvlv4CUAvSwNonteXEIHUqj5p4zdGYgCQyrv
30
+ XmlGFnzoYtCwXDPWBiVZ11NyKFl8g27c3JV6mNGaWoY/zbZYtifxo6Iv8l7MDpPq
31
+ BXDjxEsM3sPAjRnH5UGt8gFF+0qHPVDPrJSnrHYj2StSkD/k+YGFTkbr6QEVlzMa
32
+ oQ9rnGKTcTyuNDtwL8dI2+Ay10miwo9UYFUMcFQ6UCo6QhRfCrxiTeHd8F6Mz+2o
33
+ FR9USF33SMWVcExLE3wwJaEEh93XbEW8flLD3MkSILSXVG2yuJ0aLMPbfJFIErhy
34
+ Lx8rvDe6SWVyoIUMM8rJbzSPV2I9w9evPUTmJu8QQLNMzMaWwWJqTG93AZBAdWlY
35
+ +V3ectLBpuoKM8f/ZFMnUPA0mAv5e7J6u9IBwyNj/cy+wLOAbpPdmhoKZXCpQcno
36
+ ysBBJbi//0tgFWwC4vOaDMch
37
+ -----END CERTIFICATE-----
38
+ date: 2022-12-12 00:00:00.000000000 Z
39
+ dependencies:
40
+ - !ruby/object:Gem::Dependency
41
+ name: chef
42
+ requirement: !ruby/object:Gem::Requirement
43
+ requirements:
44
+ - - "<="
45
+ - !ruby/object:Gem::Version
46
+ version: '17.10'
47
+ type: :runtime
48
+ prerelease: false
49
+ version_requirements: !ruby/object:Gem::Requirement
50
+ requirements:
51
+ - - "<="
52
+ - !ruby/object:Gem::Version
53
+ version: '17.10'
54
+ - !ruby/object:Gem::Dependency
55
+ name: test-kitchen
56
+ requirement: !ruby/object:Gem::Requirement
57
+ requirements:
58
+ - - "<"
59
+ - !ruby/object:Gem::Version
60
+ version: '4'
61
+ type: :runtime
62
+ prerelease: false
63
+ version_requirements: !ruby/object:Gem::Requirement
64
+ requirements:
65
+ - - "<"
66
+ - !ruby/object:Gem::Version
67
+ version: '4'
68
+ - !ruby/object:Gem::Dependency
69
+ name: cucumber
70
+ requirement: !ruby/object:Gem::Requirement
71
+ requirements:
72
+ - - "<="
73
+ - !ruby/object:Gem::Version
74
+ version: '8.0'
75
+ type: :runtime
76
+ prerelease: false
77
+ version_requirements: !ruby/object:Gem::Requirement
78
+ requirements:
79
+ - - "<="
80
+ - !ruby/object:Gem::Version
81
+ version: '8.0'
82
+ description: Using Chef cookbook style and force any script using it to switch to
83
+ chef even if it is not install. It will install it tho ;)
84
+ email:
85
+ - jimbo_dragon@hotmail.com
86
+ executables:
87
+ - jimbodragon_acceptance_test
88
+ extensions: []
89
+ extra_rdoc_files:
90
+ - README.md
91
+ - LICENSE
92
+ files:
93
+ - LICENSE
94
+ - README.md
95
+ - bin/jimbodragon_acceptance_test
96
+ homepage: https://github.com/JimboDragonGit/jimbodragon_acceptance_test
97
+ licenses:
98
+ - MIT
99
+ metadata:
100
+ bug_tracker_uri: https://github.com/JimboDragonGit/jimbodragon_acceptance_test/issues
101
+ changelog_uri: https://github.com/JimboDragonGit/jimbodragon_acceptance_test/releases
102
+ homepage_uri: https://github.com/JimboDragonGit/jimbodragon_acceptance_test
103
+ post_install_message:
104
+ rdoc_options:
105
+ - "--charset=UTF-8"
106
+ require_paths:
107
+ - lib
108
+ required_ruby_version: !ruby/object:Gem::Requirement
109
+ requirements:
110
+ - - ">="
111
+ - !ruby/object:Gem::Version
112
+ version: '0'
113
+ required_rubygems_version: !ruby/object:Gem::Requirement
114
+ requirements:
115
+ - - ">="
116
+ - !ruby/object:Gem::Version
117
+ version: '0'
118
+ requirements: []
119
+ rubygems_version: 3.2.32
120
+ signing_key:
121
+ specification_version: 4
122
+ summary: A auto chef bootstrapper and wrapper cookbook to deploy code
123
+ test_files: []
metadata.gz.sig ADDED
Binary file