This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 113
feat: Adding implementation of startWithEncryptionKey api call #539
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
google-cla
bot
added
the
cla: yes
This human has signed the Contributor License Agreement.
label
Jan 15, 2021
product-auto-label
bot
added
the
api: compute
Issues related to the googleapis/nodejs-compute API.
label
Jan 15, 2021
Codecov Report
@@ Coverage Diff @@
## master #539 +/- ##
=======================================
Coverage 99.61% 99.61%
=======================================
Files 22 22
Lines 11948 11996 +48
=======================================
+ Hits 11902 11950 +48
Misses 46 46
Continue to review full report at Codecov.
|
akowalsk
changed the title
feat[vm]: Adding implementation of startWithEncryptionKey api call
feat: Adding implementation of startWithEncryptionKey api call
Jan 15, 2021
SurferJeffAtGoogle
added
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Jun 28, 2021
yoshi-kokoro
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Jun 28, 2021
SurferJeffAtGoogle
added
the
owlbot:run
Add this label to trigger the Owlbot post processor.
label
Jun 29, 2021
gcf-owl-bot
bot
removed
the
owlbot:run
Add this label to trigger the Owlbot post processor.
label
Jun 29, 2021
SurferJeffAtGoogle
approved these changes
Jun 29, 2021
gcf-merge-on-green bot
pushed a commit
that referenced
this pull request
Jun 29, 2021
🤖 I have created a release \*beep\* \*boop\* --- ## [2.6.0](https://www.github.com/googleapis/nodejs-compute/compare/v2.5.1...v2.6.0) (2021-06-29) ### Features * Adding implementation of startWithEncryptionKey api call ([#539](https://www.github.com/googleapis/nodejs-compute/issues/539)) ([f8018a6](https://www.github.com/googleapis/nodejs-compute/commit/f8018a61bf0b986d6ad2d5a9216c5bcfb4bdcc6f)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
api: compute
Issues related to the googleapis/nodejs-compute API.
cla: yes
This human has signed the Contributor License Agreement.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #538 🦕