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

[Feature Request]: Add support for update key in resources definition #749

Open
rnegron opened this issue Feb 19, 2024 · 2 comments
Open

Comments

@rnegron
Copy link
Member

rnegron commented Feb 19, 2024

Current Behavior

Resources don't support more than 1 "write" action via the create key. This means that customers using resources have to "exit" out of resources to add support for update-relating write actions.

Desired Behavior / Feature Request

Update the ResourceSchema to support an optional update field. This could map to a {resourceName}Update key.

@the-csaba
Copy link
Contributor

If there is consideration to open up the resource to handle updates, then I would suggest adding delete as well. Then the whole CRUD sequence would be supported by a resource.

@Troll-of-Jom
Copy link

Troll-of-Jom commented May 26, 2024

@rnegron would like to work on this task, can you assign me this task? I am new to open source learning and adapting accordingly. Thanking you in anticipation

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

No branches or pull requests

3 participants