- gcp_tpu_node was using an old TensorFlow version, as well as using
a popular TPU variant (3-8) in a zone that had a capacity limit.
Both have been updated to working values.
- gcp_spanner_instance works, enabling for CI.
- gcp_resourcemanager_project is running into quota issues for
listing the API to verify state. Adding a to-do as well as
removing some people-specific names.
- bootstrap code was not correctly instantiating the cloud function.
- compute_instance has a typo from a previous commit.
- re-disabling forwarding rule as it still has the backend_service
fingerprint requirement
- remove the global health check (not necessary to create a backend
service)
- configure backend service to external, as internal backend services
cannot use the HTTP protocol.
The test does not yet pass due to a discovered change, but
some progress was made.
- updating disk image to an existing, non-EOL image.
- updating subnetwork configuration.
Fixing some of the existing failing tests in the CI process.
Specifically:
- gcp_appengine_firewall_rule: modified validation to support the
default firewall rule
- gcp_cloudfunctions_cloud_function: bootstrapping the required GS
bucket and files for creating a valid cloud function.
- Slight update to the functionality, which now requires a runtime
specified for new functions.
-
To help catch issues from PRs that would regress behavior,
adding a GitHub action similar to unit tests to run integration
tests.
GitHub actions do not pass secrets to actions which are triggered
by PRs sent from forks. As a result, it is not possible to have CI
run on the forks from external contributors. Currently implementing a
process that requires manual review until a more direct solution is
found.
Adding some basic instructions for future maintainers and contributors.
As a step toward adding integration testing into
the CI process for this project, adding instructions
on how to run the tests.
compute_region_disk was used as a test. Fixed
the tests which was previously hard-coded to
the `graphite-playground` GCP project to work
with the project in the user-configure .ini file.
As a first step to rehabilitate the google.cloud repository,
adding actions to help ensure that the collection is still
passing tests as changes are merged.
Details:
- ansible-devel was not added to the matrix since it may
destablize the tests, primarily used to validate the collection.
- running sanity tests reported over 100+ issues, backlogged to #498
before turning those on.
* Unnecessary "else" after "return"
* Handle if service account file is missing with proper user message
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
Signed-off-by: Modular Magician <magic-modules@google.com>
User should read GCP_SERVICE_ACCOUNT_FILE instead of
gcp_service_account_file
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
Signed-off-by: Modular Magician <magic-modules@google.com>
* Allow redisVersion to change, promoted some fields to GA
* allow updating properties if update method is defined at the field level
* upgrade post url
* fix current resources to not reference url
* add support for forceNew if version is shrinking
* don't send request if not updating anything.. request fails if update mask is empty.. also add more tests
* fix spelling mistake
* fix rake issues
* remove transcription mode... forces new on change
Signed-off-by: Modular Magician <magic-modules@google.com>
This change promotes custom_response_headers for
google_compute_backend_service and google_compute_backend_bucket
to GA.
Signed-off-by: Gorka Lerchundi Osa glertxundi@gmail.com
Signed-off-by: Modular Magician <magic-modules@google.com>
