When updating a resource that requires a fetch call should I use update or generic action?

Ash Forum Ash Questions / Help
,
1

I’m wondering what’s the good practice in this case.

I’ve got a resource named App. At some point after creation, I want to fetch some details from an endpoint and update the resource with it.

The “update” verb in that sentence made me think that, “duh, it should be an update, Rico!“. But maybe that would hold the db transaction open throughout the duration of the action.

If I use the `change` argument in an update action, make the call there, it should be ok, correct?

2

Have a look here: Actions — ash v3.6.3

Best practice says “Use before_transaction for external API calls”.

I would keep everything that relates to the creation of this resource in the same action. Actions should be specific and encapsulate a process. They are not supposed to be generic “create” actions as an example.