This repository has been archived by the owner on Jun 14, 2021. It is now read-only.
Feature/network zones #201
Merged
Conversation
This file contains 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
added 8 commits
June 25, 2019 14:56
quantumew
reviewed
Jul 3, 2019
quantumew
approved these changes
Jul 3, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I implemented a resource that will allow to create and manage network zones.
API Reference: https://developer.okta.com/docs/reference/api/zones/
Please note that the "Dynamic" feature needs to be enabled in your Okta in order to work. To get this it should be enough to get in touch with their support team, as it seems to be an early access feature.
Also please note that I'm way far from being a GO developer, I'm open to any suggestion.