WIP: Add mock for AlloyDB User #1845
Draft
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
|
[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 |
…fter delete More see b/339458480
* docs: add feature docs Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com> * docs: also link from release notes Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com> * Apply suggestions from code review --------- Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>
The older version has a CVE (though it does not appear to be reachable)
Wiring up support for our direct controllers here.
A step in running samples more like fixtures.
This was auto-generated using the dev-to-proto tool, and then a few fixes were made manually: * Commented out some fields that we aren't supporting yet (with NOTYET) * Changed some `*Duration` to `*string` * Fixed up the definition of `Empty` * Added `+required` annotations * Fixed up the Spec and Status * Added some registration boilerplate Also, I switched to the latest controller-gen in dev/tasks/generate-crds, so that we can use the `+required` annotation (and to pick up the omitempty fix)
We now need to support int32
This allows us to see unsupported fields.
Some APIs may include objects in maps, we want to output those objects also.
A first-pass at a tool to generate types & map functions.
Including around refs
It's not perfect (v3 vs v1 is tricky), but it's much closer.
Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>
Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>
* chore: clean apis/config dir for now Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com> * chore: autogen deepcopies Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com> * Revert "chore: autogen deepcopies" This reverts commit ecd7e8c. --------- Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>
- Move applier into pkg/applier, simplify parameters - Split Evaluate and Apply - old: expanders [evaluate + apply] - new: expanders [evaluate] , expanders [apply]
- Composition API changes
- Add .status.stages capturing individual stage validation failures
- Add .generation (to be implemented)
- Jinja2 expander changes
- unit-tests for Validate() method
- Implement Validate() method that parser script to capture syntax errors
- Add python script that calls jinjs2 parser
- Update dockerfile
- Composition controller changes
- As part of reconcile, validate all expanders and record failures in
status
- Tests
- Add TestSimpleCompositionJinjaValidationFailure that tests the jinja
syntax failure checks
The test.cnrm.cloud.google.com/reconcile-cookie annotation can be changed without affecting the "true" desired state, but we special case the annotation in our filtering, so that it still triggers the reconciler. Co-authored-by: alex <8968914+acpana@users.noreply.github.com>
Extract the KCC version into its own file. Make it available for embed to pull it in. Make sure that its available in the docker file.
…/google-beta/fwtransport/version.txt
Generated from the proto by dev/tools/proto-to-mapper and then lightly edited / moved around.
We aim to construct a readable version of the GRPC requests.
This uses our new GRPC collection infrastructure.
This should allow matching of more complex paths (as found in servicenetworking)
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.
Change description
Fixes #
Tests you have done
make ready-prto ensure this PR is ready for review.