Fix TLS struct keys and adjust field tags to match field names #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The previous update to enable TLS config settings leveraged existing structs which, when mapped from JS -> Golang, did not end up with a friendly user interface. Here we clean up the struct fields after reading the following docs.
https://grafana.com/docs/k6/latest/extensions/explanations/go-js-bridge/#about-the-go-to-js-bridge
Also update the docker examples to match the new struct keys.