Hi there! We are hard at work preparing to release a significant enhancement to our GCP Committed Use Discount (CUD) feature. To take advantage of the new feature, there is a simple action required on your part to grant a new permission to your GCP Ternary service account. The new permission is compute.commitments.list  We recommend adding the permission now to avoid a disruption when the feature goes live. We plan to launch the new feature in early January 2023.

If you created a custom role in your GCP environment and assigned the role to your GCP Ternary service account, simply edit the custom role adding the compute.commitments. list permission to the role. That's it.

If you assigned built-in GCP roles to your GCP Ternary service account, we recommend creating the custom role described in our GCP Onboarding Instructions. In the onboarding instructions, jump down to Step 4. Grant Ternary Permissions using Cloud Shell or CLI to create your custom role and bind the role to your Ternary service account. You only need to complete Step 4. After successfully creating the custom role and binding the role to your Ternary service account, you can safely remove the built-in GCP roles assignments from your Ternary service account. 

Going forward, we will update the YAML and Terraform files in our Github repo with any new GCP permissions required for future features. We believe this approach follows the best practice of least privilege assigning only the specific permissions Ternary requires to your Ternary service account.