This repository has been archived by the owner on May 31, 2024. It is now read-only.
Bumped up idl to use insecureVerify flag for remote and fixed docs #125
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.
Signed-off-by: Prafulla Mahindrakar prafulla.mahindrakar@gmail.com
TL;DR
Using insecureVerify to disregard the hostname coming in the cert for testing flyte on remote.
Customers can try this initially before productionizing with a CA cert.
Also fixed the docs to included the missing generated files
https://docs.flyte.org/projects/flytectl/en/pmahindrakar-bump-idl/
Modified the config.yaml to use the insecureVerify flag
Without the flag
Type
Are all requirements met?
Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/lyft/flyte/issues/
Follow-up issue
NA
OR
https://github.com/lyft/flyte/issues/