-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] WIP: Skip calling Read after Create/Update operations for notebooks #4173
Open
alexott
wants to merge
2
commits into
main
Choose a base branch
from
notebooks-skip-get-status
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
alexott
temporarily deployed
to
test-trigger-is
October 30, 2024 12:21
— with
GitHub Actions
Inactive
mgyucht
reviewed
Oct 30, 2024
alexott
changed the title
[Fix] Skip calling
[Feature] Allow to skip calling Read after Create/Update operations
Oct 30, 2024
get-status
for notebooks in Read after Create/Update operations
alexott
changed the title
[Feature] Allow to skip calling Read after Create/Update operations
[Feature] WIP: Allow to skip calling Read after Create/Update operations
Oct 30, 2024
alexott
force-pushed
the
notebooks-skip-get-status
branch
from
October 30, 2024 17:46
7ecd15c
to
2ddb757
Compare
alexott
temporarily deployed
to
test-trigger-is
October 30, 2024 17:46
— with
GitHub Actions
Inactive
alexott
changed the title
[Feature] WIP: Allow to skip calling Read after Create/Update operations
[Feature] WIP: Skip calling Read after Create/Update operations for notebooks
Nov 3, 2024
alexott
added a commit
that referenced
this pull request
Nov 3, 2024
This PR adds the ability for a resource to specify that it may not need to call `Read` after `Create` and `Update` operations so we can avoid performing another API call(s). The resource may implement `CanSkipReadAfterCreateAndUpdate` function that can decide if the `Read` operation should be skipped. I decided to move common part from #4173 to make it easier to review
5 tasks
github-merge-queue bot
pushed a commit
that referenced
this pull request
Nov 4, 2024
## Changes <!-- Summary of your changes that are easy to understand --> This PR adds the ability for a resource to specify that it may not need to call `Read` after `Create` and `Update` operations so we can avoid performing another API call(s). The resource may implement `CanSkipReadAfterCreateAndUpdate` function that can decide if the `Read` operation should be skipped. I decided to move common part from #4173 to make it easier to review ## Tests <!-- How is this tested? Please see the checklist below and also describe any other relevant tests --> - [x] `make test` run locally - [ ] relevant change in `docs/` folder - [ ] covered with integration tests in `internal/acceptance` - [x] relevant acceptance tests are passing - [ ] using Go SDK
It was found that the import API returns `object_id` as a result of its execution, so we don't really need to call get-status to fill all attributes. This should help when we import a large number of notebooks, i.e., when applying exported resources. This also changes `format` and `language` attributes to `optional,computed` to avoid having issues with defaults, and suppress diff.
alexott
force-pushed
the
notebooks-skip-get-status
branch
from
November 5, 2024 13:49
2ddb757
to
e80cda6
Compare
alexott
temporarily deployed
to
test-trigger-is
November 5, 2024 13:50
— with
GitHub Actions
Inactive
alexott
temporarily deployed
to
test-trigger-is
November 5, 2024 13:50
— with
GitHub Actions
Inactive
alexott
temporarily deployed
to
test-trigger-is
November 6, 2024 10:26
— with
GitHub Actions
Inactive
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
alexott
temporarily deployed
to
test-trigger-is
November 6, 2024 10:26
— with
GitHub Actions
Inactive
Test Details: go/deco-tests/11701693302 |
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.
Changes
It's based on #4190.
It was found that the
import
API returnsobject_id
as a result of its execution, so we don't really need to callget-status
to fill all attributes. This should help when we import a large number of notebooks, i.e., when applying exported resources.TODOs:
language
attributeTests
make test
run locallyrelevant change indocs/
folderinternal/acceptance
using Go SDK