Skip to content
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

Create the Operation common component. #8

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

rofrankel
Copy link
Contributor

This is based on Google's google.longrunning.Operation.

@rofrankel rofrankel requested a review from a team as a code owner March 8, 2024 21:36
rofrankel added a commit to aep-dev/aeps that referenced this pull request Mar 8, 2024
The changes are pretty broad, and include:

1) Refer to operations rather than status monitors.  This is based on discussion in Slack with Luke Sneeringer, who originally adopted this AEP.
2) Add references to the common components repo (aep-dev/aep) and perform corresponding cleanup in the examples.

This PR corresponds to aep-dev/aep-components#8.
rofrankel added a commit to aep-dev/aeps that referenced this pull request Mar 8, 2024
The changes are pretty broad, and include:

1) Refer to operations rather than status monitors.  This is based on discussion in Slack with Luke Sneeringer, who originally adopted this AEP.
2) Add references to the common components repo (aep-dev/aep) and perform corresponding cleanup in the examples.

This PR corresponds to aep-dev/aep-components#8.
rofrankel added a commit to aep-dev/aeps that referenced this pull request Mar 8, 2024
The changes are pretty broad, and include:

1) Refer to operations rather than status monitors.  This is based on discussion in Slack with Luke Sneeringer, who originally adopted this AEP.
2) Add references to the common components repo (aep-dev/aep) and perform corresponding cleanup in the examples.

This PR corresponds to aep-dev/aep-components#8.
rofrankel added a commit to aep-dev/aeps that referenced this pull request Mar 8, 2024
The changes are pretty broad, and include:

1) Refer to operations rather than status monitors.  This is based on discussion in Slack with Luke Sneeringer, who originally adopted this AEP.
2) Add references to the common components repo (aep-dev/aep) and perform corresponding cleanup in the examples.

This PR corresponds to aep-dev/aep-components#8.
rofrankel added a commit to aep-dev/aeps that referenced this pull request Mar 8, 2024
The changes are pretty broad, and include:

1) Refer to operations rather than status monitors.  This is based on discussion in Slack with Luke Sneeringer, who originally adopted this AEP.
2) Add references to the common components repo (aep-dev/aep) and perform corresponding cleanup in the examples.

This PR corresponds to aep-dev/aep-components#8.
rofrankel added a commit to aep-dev/aeps that referenced this pull request Mar 11, 2024
* Clean up and modernize AIP-151: Long-running operations.

The changes are pretty broad, and include:

1) Refer to operations rather than status monitors.  This is based on discussion in Slack with Luke Sneeringer, who originally adopted this AEP.
2) Add references to the common components repo (aep-dev/aep) and perform corresponding cleanup in the examples.

This PR corresponds to aep-dev/aep-components#8.

* lint

* Update creation date

* Update aep/general/0151/aep.yaml

Co-authored-by: Yusuke Tsutsumi <[email protected]>

---------

Co-authored-by: Yusuke Tsutsumi <[email protected]>
Copy link

@jeremyfiel jeremyfiel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple comments on the schema.

If true, the operation is completed, and either response or error
is available.
error:
$ref: '#/components/schemas/Error'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this doesn't resolve to anything and you don't have the schema defined with the same language as the markdown description. Error and response are mutually exclusive in the text, but not here.

@@ -0,0 +1,32 @@
Operation:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no $schema, title, description, or $id defined for this schema.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants