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

Flow Support (All Resources) #13

Open
steve-r-west opened this issue May 12, 2021 · 0 comments
Open

Flow Support (All Resources) #13

steve-r-west opened this issue May 12, 2021 · 0 comments

Comments

@steve-r-west
Copy link
Collaborator

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):

resource "epcc_customer" "my_customer" { 
    name = "Jane Smith"
    email = "[email protected]"
    flows { 
          "somekey" = "someValue" 
          }
} 

There are some additional challenges with this, because it may not just be string types.

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

2 participants