WIP: Reproduce bigtable issue #1780
Open
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
Collaborator
justinsb
commented
May 13, 2024
justinsb
commented
- tfprovider: support intercepting GRPC requests
- tests: record grpc requests in our golden tests
- tests: capture golden output for bigtabletable test
- mockgcp: Support for bigtable
- mockgcp: Support BigtableTable
- tests: capture golden output for bigtable
- Create bigtable test
- WIP: tests - try client-side update
- tests: export BigtableInstance
- powertool: change-state-into-spec can remove fields set by state-into-spec
- tests: start to refactor normalization logic out of specific tests
- tests: Add ability to run CLI to script_test
- tests: Create change-state-into-spec powertool test scenario
- tests: Create test scenario for force-set-field powertool
- test with powertool
- WIP
- fix merge
- tests
- test with mocks
- bigtable: better mockgcp
- WIP: script test with client-side apply
- capture generated real output
- mockgcp: Generate grpc bindings for bigtable
- mockgcp: better support for updateMask
- mockgcp: more bigtable
- mockgcp: bigtable can serve on http also
- autogen: generated bigtable grpc-gateway bindings
- direct actuation: BigtableInstance
- undo managedFields change
- Rebase fixes
- Split out bigtable testfixutes
- mockgcp: better handling of invalid bigtable cluster configuration
- test passing by appending & state-into-spec:absent
- failing tests
We aim to construct a readable version of the GRPC requests.
This uses our new GRPC collection infrastructure.
This is tricky because our current is actually not using REST (uniquely so!), so our normal interception method doesn't work.
Note this service is implemented via GRPC, so we need some more complex interception.
…-spec Using the field manager, we can detect and remove any fields that were set by state-into-spec.
This way our various tests can share one normalization function
This enables us to test our powertools in our existing framework
Changing the location of a StorageBucket is a good example usage.
Trying something different: grpc binding to the "real" google protos.
Filter both body & query parameters, to map json style field-names to proto fields.
This uses the grpc-gateway generated code only
A slightly complex resource because of the Cluster subresources
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.