-
Notifications
You must be signed in to change notification settings - Fork 48
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
Support for Map[string]string #80
Comments
Hi @dikhan do you have any work done on this subject or any ideas how to approach it? |
Hey @fredericosilva , We are planning to work on this next after the #186 is done. Haven't put much thought on it besides the initial research when creating the issue, but the idea would be to have the provider understand properties that are\ defined as follows and expose their terraform schema as a
If you fancy taking a stub at it, the two places to look into would be:
I would start putting together a test in https://github.com/dikhan/terraform-provider-openapi/blob/master/tests/e2e/resources_test.go that has the map described and asserting on the provider schema containing the hashmap which would fail. That could serve as the basic to get going and start drilling into the code to understand better the different places that need updates. Hope this helps! |
Thank you for pointing me in the right direction. I'll try to have a look on that later this week. |
Is your feature request related to a problem?
Currently, the provider only supports complex object data structures (with nested properties etc) but it's not possible to have properties that are Map[string]string.
Describe the solution you'd like
As per swagger spec HashMaps of key/value strings can be described as follows:
And the expectation would be to have that property translated to the following terraform schema which effectively is a Map[string]string:
Acceptance criteria
What's required to consider this feature request complete?
Checklist
Don't forget to go through the checklist to make sure the issue is created properly:
The text was updated successfully, but these errors were encountered: