Skip to content

Releases: oracle/terraform-provider-oci

Bug Fixes and VNIC skip_source_dest_check

26 Sep 22:39
Compare
Choose a tag to compare
  • Resources are now removed from the state file if in a "terminated" state so that it is recreated on an apply (#113)
  • Adds VNIC skip_source_dest_check property
  • Enable empty route rules (#68)
  • Fix import of Subnet prohibit_public_ip_on_vnic
  • Adds pagination to all IAM data sources
  • General fixes for plans including compartments as a resource

If upgrading from v1, see this wiki for migration steps.

New provider name "terraform-provider-oci"

14 Sep 00:56
Compare
Choose a tag to compare
  • changes name from terraform-provider-baremetal to terraform-provider-oci
    • see this wiki on migration steps and associated migration tool usage instructions.
  • adds support for Secondary Private IPs

Multi-VNIC and bug fixes

31 Aug 22:04
Compare
Choose a tag to compare
  • Added VNIC Attachment resource for Multi-VNIC support
  • Fix for bug when restoring volume backups (#231)
  • Fix issue with block volume recreating on every apply (#222)

DBSystem Exadata shapes, instance nested metadata, bug fixes, doc updates

11 Aug 21:37
Compare
Choose a tag to compare

-Fixes for DBSystem and enabling Exadata Shapes
-Enabling nested metadata in compute Instances
-Making metadata an optional parameter in compute instances
-Fixing isStateful bug in security lists
-Adding DHCP Options examples
-Docs and example updates

Option to disable automatic retries as a short term soln to issue #179

20 Jul 01:11
Compare
Choose a tag to compare

In v.1.0.14 we introduced automatic retry logic to fix some eventual consistency issues. The retries significantly affected the performance of destroy operations. In v1.0.16 we have added an option to disable the automatic retries. A limited number of resources had issues that were solved by the retry logic so we are adding this option as a short term fix. We are working on a better solution.
To avoid the longer time on destroy operations you can set the disable_auto_retries to true in the baremetal provider. See an example in docs/examples/compute/single_instance/provider.tf

Some people also reported they were seeing an error in some operating systems when a retry token was being used for multiple requests (See issue #170). v1.0.16 also includes a fix for this. We cannot test on every possible environment so please let us know if you are still seeing this issue when the automatic retries are enabled.

Bug Fixes

14 Jul 01:07
Compare
Choose a tag to compare

Bug fixes for:

  • DBaaS DBSystem
  • Object Storage preauthenticated requests
  • Identity User UI password
  • Add missing display name updates to security lists and route tables

Pre-authenticated object requests, enhanced retry logic, private load balancer and persistent sessions

29 Jun 07:50
Compare
Choose a tag to compare
  • pre-authenticated object store requests
  • load balancer support for local vcn and persistent sessions
  • enhanced retry logic for request failures
    • typical network operations retry for 2 minutes
    • replication dependent operations retry for 10 minutes

Bug fixes

19 Jun 07:57
Compare
Choose a tag to compare
  • load balancer bug fixes
  • supports public buckets
  • adds retry logic for request failures

Bug fixes

26 May 20:46
Compare
Choose a tag to compare
  • load balancer backend set bug fix #85
  • fixes IPSec error #107
  • fixes #99 (doc error)

Bug fixes, acceptance tests

20 May 05:32
Compare
Choose a tag to compare
  • load balancer bug fixes
  • emit terraform-provider-baremetal plugin version number in debug output