Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oci_database_db_system forces new resource with change to cpu_core_count #517

Closed
drauba opened this issue Apr 28, 2018 · 3 comments
Closed
Assignees
Labels

Comments

@drauba
Copy link

drauba commented Apr 28, 2018

Terraform Version

Terraform v0.11.7

OCI Provider Version

terraform-provider-oci 2.1.5

Description:

Changing cpu_core_count on a database system forces a new resource. This action can be completed with the oci cli without recreating the database system.

Terraform Plan

Feature request.

@parweza
Copy link
Contributor

parweza commented Apr 30, 2018

Thanks for the feedback. I have added this to our backlog to help us prioritize this for upcoming releases of the provider.

@anandhmahal anandhmahal added parity OCI service feature missing in provider and removed enhancement labels May 16, 2018
@drauba
Copy link
Author

drauba commented May 23, 2018

Would the change be as simple as updating this piece of code from database_db_system_resource.go?

"cpu_core_count": { Type: schema.TypeInt, Required: true, ForceNew: true, // todo: remove when update is supported }

@rcohenma rcohenma self-assigned this Jun 19, 2018
@codycushing codycushing added bug and removed in progress parity OCI service feature missing in provider labels Jul 3, 2018
@codycushing
Copy link
Contributor

Hello, this has been addressed in release 2.1.13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants