Add support for Oracle Cloud Infrastructure (OCI) DNS #860
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
|
Tests are now working so I have squashed my commits accordingly. |
The Oracle Cloud Infrastructure (OCI) provider can create, list, update and delete records in any public DNS zone hosted in a tenancy located in any region within the OCI commercial (OC1) realm. No authentication details are required if the OCI CLI installed and the DEFAULT profile configured in the ~/.oci/config file has the appropriate permission for the target DNS zone. Use the --auth-file and --auth-profile command-line parameters or the LEXICON_OCI_AUTH_FILE and LEXICON_OCI_AUTH_PROFILE environment variables to override the default file location and profile name. Set the --auth-type parameter to 'instance_principal' to use instance principal authentication when running Lexicon on an Oracle Cloud Infrastructure compute instance. This method requires permission to be granted via IAM policy to a dynamic group that includes the compute instance. See <https://docs.oracle.com/en-us/iaas/Content/DNS/Concepts/dnszonemanagement.htm> for in-depth documentation on managing DNS via the OCI console, SDK or API. Signed-off-by: Avi Miller <avi.miller@oracle.com>
adferrand
approved these changes
Aug 9, 2021
|
Thanks! I was just about to ask if there was anything I still needed to do. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 Oracle Cloud Infrastructure (OCI) provider can create, list, update and
delete records in any public DNS zone hosted in a tenancy located in any
region within the OCI commercial (OC1) realm.
No authentication details are required if the OCI CLI installed and the DEFAULT
profile configured in the
~/.oci/configfile has the appropriate permission forthe target DNS zone.
Use the
--auth-*command-line parameters or theLEXICON_OCI_AUTH_*environment variables tooverride the default file location and profile name.
Set the
--auth-typeparameter toinstance_principalto use instance principalauthentication when running Lexicon on an Oracle Cloud Infrastructure compute
instance. This method requires permission to be granted via IAM policy to a
dynamic group that includes the compute instance.
See https://docs.oracle.com/en-us/iaas/Content/DNS/Concepts/dnszonemanagement.htm
for in-depth documentation on managing DNS via the OCI console, SDK or API.
Signed-off-by: Avi Miller avi.miller@oracle.com