google-cloud-env 1.0.3 → 1.0.4

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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 7fb29068180ec1331d9cefca4af08d2897d27a939736508cb10062348f2dd25a
4
- data.tar.gz: 2732b7f80957d4f5bd0ed8c90ed2ae513dbe0b4d139ada75cf44a28d21178f55
3
+ metadata.gz: b4d7bd0ad488e1a5d0baf5d66472abb9863763ccb6a3f47594d6d5e14679a197
4
+ data.tar.gz: fc56bed9e32b93c7860ce381eb3b823776785ad2b7bfe0e999a93df250cfca24
5
5
  SHA512:
6
- metadata.gz: 2d0bb7a431484820e559f1371a3e11842b305d3762df200d34d4ca1c98552ed5495995e94b75feda46114763e3e62a4dd675418bf1544bcf38a345fe4303d503
7
- data.tar.gz: e151394bb98932109e4570c713d7cc7af7a56c8c66dee8064bfa5c00c58e7402a19ba8fba5f5f6239df6554e65c235db4ecd78941cbb413935e68186278fa137
6
+ metadata.gz: c1b75939008a21c63ca4f56ef9eb8084b21e9381657e39ccb4be4393663b90e9ed54389babde2eff0e8227363ae871d927e8c7876db885caeacd4a439483e664
7
+ data.tar.gz: f7db960beed744381757e65f0da835048d2c5c000ddb2fecbb911feb0d6d72f1aa2ef6942ddc6ffea94466e8c18e3176e791b3b413ad194c87856975c0574943
@@ -0,0 +1,23 @@
1
+ # Release History
2
+
3
+ ### 1.0.4 / 2018-09-12
4
+
5
+ * Add missing documentation files to package.
6
+
7
+ ### 1.0.3 / 2018-09-10
8
+
9
+ * Update documentation.
10
+
11
+ ### 1.0.2 / 2018-06-28
12
+
13
+ * Use Kubernetes Engine names.
14
+ * Alias old method names for backwards compatibility.
15
+ * Handle EHOSTDOWN error when connecting to env.
16
+
17
+ ### 1.0.1 / 2017-07-11
18
+
19
+ * Update gem spec homepage links.
20
+
21
+ ### 1.0.0 / 2017-03-31
22
+
23
+ * Initial release
@@ -0,0 +1,40 @@
1
+ # Contributor Code of Conduct
2
+
3
+ As contributors and maintainers of this project, and in the interest of
4
+ fostering an open and welcoming community, we pledge to respect all people who
5
+ contribute through reporting issues, posting feature requests, updating
6
+ documentation, submitting pull requests or patches, and other activities.
7
+
8
+ We are committed to making participation in this project a harassment-free
9
+ experience for everyone, regardless of level of experience, gender, gender
10
+ identity and expression, sexual orientation, disability, personal appearance,
11
+ body size, race, ethnicity, age, religion, or nationality.
12
+
13
+ Examples of unacceptable behavior by participants include:
14
+
15
+ * The use of sexualized language or imagery
16
+ * Personal attacks
17
+ * Trolling or insulting/derogatory comments
18
+ * Public or private harassment
19
+ * Publishing other's private information, such as physical or electronic
20
+ addresses, without explicit permission
21
+ * Other unethical or unprofessional conduct.
22
+
23
+ Project maintainers have the right and responsibility to remove, edit, or reject
24
+ comments, commits, code, wiki edits, issues, and other contributions that are
25
+ not aligned to this Code of Conduct. By adopting this Code of Conduct, project
26
+ maintainers commit themselves to fairly and consistently applying these
27
+ principles to every aspect of managing this project. Project maintainers who do
28
+ not follow or enforce the Code of Conduct may be permanently removed from the
29
+ project team.
30
+
31
+ This code of conduct applies both within project spaces and in public spaces
32
+ when an individual is representing the project or its community.
33
+
34
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
35
+ reported by opening an issue or contacting one or more of the project
36
+ maintainers.
37
+
38
+ This Code of Conduct is adapted from the [Contributor
39
+ Covenant](http://contributor-covenant.org), version 1.2.0, available at
40
+ [http://contributor-covenant.org/version/1/2/0/](http://contributor-covenant.org/version/1/2/0/)
@@ -0,0 +1,123 @@
1
+ # Contributing to Google Cloud hosting environment
2
+
3
+ 1. **Sign one of the contributor license agreements below.**
4
+ 2. Fork the repo, develop and test your code changes.
5
+ 3. Send a pull request.
6
+
7
+ ## Contributor License Agreements
8
+
9
+ Before we can accept your pull requests you'll need to sign a Contributor
10
+ License Agreement (CLA):
11
+
12
+ - **If you are an individual writing original source code** and **you own the
13
+ intellectual property**, then you'll need to sign an [individual
14
+ CLA](https://developers.google.com/open-source/cla/individual).
15
+ - **If you work for a company that wants to allow you to contribute your work**,
16
+ then you'll need to sign a [corporate
17
+ CLA](https://developers.google.com/open-source/cla/corporate).
18
+
19
+ You can sign these electronically (just scroll to the bottom). After that, we'll
20
+ be able to accept your pull requests.
21
+
22
+ ## Setup
23
+
24
+ In order to use the google-cloud-env console and run the project's tests,
25
+ there is a small amount of setup:
26
+
27
+ 1. Install Ruby. google-cloud-env requires Ruby 2.3+. You may choose to
28
+ manage your Ruby and gem installations with [RVM](https://rvm.io/),
29
+ [rbenv](https://github.com/rbenv/rbenv), or
30
+ [chruby](https://github.com/postmodern/chruby).
31
+
32
+ 2. Install [Bundler](http://bundler.io/).
33
+
34
+ ```sh
35
+ $ gem install bundler
36
+ ```
37
+
38
+ 3. Install the top-level project dependencies.
39
+
40
+ ```sh
41
+ $ bundle install
42
+ ```
43
+
44
+ 4. Install the hosting environment dependencies.
45
+
46
+ ```sh
47
+ $ cd google-cloud-env/
48
+ $ bundle exec rake bundleupdate
49
+ ```
50
+
51
+ ## Console
52
+
53
+ In order to run code interactively, you can automatically load
54
+ google-cloud-env and its dependencies in IRB. This requires that your
55
+ developer environment has already been configured by following the steps
56
+ described in the {file:AUTHENTICATION.md Authentication Guide}. An IRB console
57
+ can be created with:
58
+
59
+ ```sh
60
+ $ cd google-cloud-env/
61
+ $ bundle exec rake console
62
+ ```
63
+
64
+ ## hosting environment Tests
65
+
66
+ Tests are very important part of google-cloud-env. All contributions
67
+ should include tests that ensure the contributed code behaves as expected.
68
+
69
+ To run the unit tests, documentation tests, and code style checks together for a
70
+ package:
71
+
72
+ ``` sh
73
+ $ cd google-cloud-env/
74
+ $ bundle exec rake ci
75
+ ```
76
+
77
+ To run the command above, plus all acceptance tests, use `rake ci:acceptance` or
78
+ its handy alias, `rake ci:a`.
79
+
80
+ ### hosting environment Unit Tests
81
+
82
+
83
+ The project uses the [minitest](https://github.com/seattlerb/minitest) library,
84
+ including [specs](https://github.com/seattlerb/minitest#specs),
85
+ [mocks](https://github.com/seattlerb/minitest#mocks) and
86
+ [minitest-autotest](https://github.com/seattlerb/minitest-autotest).
87
+
88
+ To run the hosting environment unit tests:
89
+
90
+ ``` sh
91
+ $ cd google-cloud-env/
92
+ $ bundle exec rake test
93
+ ```
94
+
95
+ ### hosting environment Documentation Tests
96
+
97
+ The project tests the code examples in the gem's
98
+ [YARD](https://github.com/lsegal/yard)-based documentation.
99
+
100
+ The example testing functions in a way that is very similar to unit testing, and
101
+ in fact the library providing it,
102
+ [yard-doctest](https://github.com/p0deje/yard-doctest), is based on the
103
+ project's unit test library, [minitest](https://github.com/seattlerb/minitest).
104
+
105
+ To run the hosting environment documentation tests:
106
+
107
+ ``` sh
108
+ $ cd google-cloud-env/
109
+ $ bundle exec rake doctest
110
+ ```
111
+
112
+ If you add, remove or modify documentation examples when working on a pull
113
+ request, you may need to update the setup for the tests. The stubs and mocks
114
+ required to run the tests are located in `support/doctest_helper.rb`. Please
115
+ note that much of the setup is matched by the title of the
116
+ [`@example`](http://www.rubydoc.info/gems/yard/file/docs/Tags.md#example) tag.
117
+ If you alter an example's title, you may encounter breaking tests.
118
+
119
+ ## Code of Conduct
120
+
121
+ Please note that this project is released with a Contributor Code of Conduct. By
122
+ participating in this project you agree to abide by its terms. See
123
+ {file:CODE_OF_CONDUCT.md Code of Conduct} for more information.
@@ -16,7 +16,7 @@
16
16
  module Google
17
17
  module Cloud
18
18
  class Env
19
- VERSION = "1.0.3".freeze
19
+ VERSION = "1.0.4".freeze
20
20
  end
21
21
  end
22
22
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-cloud-env
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.3
4
+ version: 1.0.4
5
5
  platform: ruby
6
6
  authors:
7
7
  - Daniel Azuma
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2018-09-10 00:00:00.000000000 Z
11
+ date: 2018-09-12 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: faraday
@@ -175,6 +175,9 @@ extensions: []
175
175
  extra_rdoc_files: []
176
176
  files:
177
177
  - ".yardopts"
178
+ - CHANGELOG.md
179
+ - CODE_OF_CONDUCT.md
180
+ - CONTRIBUTING.md
178
181
  - LICENSE
179
182
  - README.md
180
183
  - lib/google-cloud-env.rb