feat: clientvpnendpoint #416
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
lmouhib force-pushed the feat/clientvpnendpoint branch 2 times, most recently from 9e8a619 to 806b9da Compare 
lmouhib reviewed Feb 19, 2024
lmouhib force-pushed the feat/clientvpnendpoint branch from 145572c to bbb34b3 Compare lmouhib approved these changes Feb 20, 2024
lmouhib force-pushed the feat/clientvpnendpoint branch from bbb34b3 to 1d2adfb Compare Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
Description of changes:
Client VPN ednpoint implementation with SAML authentication as an optional feature of DataVpc construct
Checklist
fix:,feat:,docs:, ...)By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.