You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My believe is that we would need to change every resource in the platform to essentially also have a map[string]interface{} or something and ensure the HTTP layer can handle arbitrary keys and values on any resource, and that the API is such that it is managable.
Then we need to put this in terraform, I recommend in terraform that we use a distinct value and not embed the data in the object (i.e., in terraform we would have):
Once we have implemented #7, #11 and #12 we should have all the pieces necessary to create flows in the platform.
https://documentation.elasticpath.com/commerce-cloud/docs/concepts/custom-data-flows.html
https://documentation.elasticpath.com/commerce-cloud/docs/developer/how-to/extend-any-resource.html
My believe is that we would need to change every resource in the platform to essentially also have a map[string]interface{} or something and ensure the HTTP layer can handle arbitrary keys and values on any resource, and that the API is such that it is managable.
Then we need to put this in terraform, I recommend in terraform that we use a distinct value and not embed the data in the object (i.e., in terraform we would have):
There are some additional challenges with this, because it may not just be string types.
The text was updated successfully, but these errors were encountered: