Skip to content

Work around CUR 2.0 provider bug: declare BILLING_VIEW_ARN#116

Closed
Alexanderamiri wants to merge 2 commits into
mainfrom
fix/cur-billing-view-arn
Closed

Work around CUR 2.0 provider bug: declare BILLING_VIEW_ARN#116
Alexanderamiri wants to merge 2 commits into
mainfrom
fix/cur-billing-view-arn

Conversation

@Alexanderamiri
Copy link
Copy Markdown
Member

AWS returns BILLING_VIEW_ARN in the CreateExport response even when not set, causing Terraform's "inconsistent result after apply" error. Declaring it as empty string prevents the drift.

Ref: hashicorp/terraform-provider-aws#42761

AWS returns BILLING_VIEW_ARN in the CreateExport response even when not
set, causing "inconsistent result after apply". Declaring it as empty
string prevents the drift.

Ref: github.com/hashicorp/terraform-provider-aws/issues/42761
@Alexanderamiri Alexanderamiri requested a review from a team as a code owner March 27, 2026 15:36
@Alexanderamiri Alexanderamiri enabled auto-merge (squash) March 27, 2026 15:36
bcm-data-exports:GetExport is not included in the ReadOnlyAccess managed
policy (newer service). Add explicit read permissions so terraform plan
can read CUR 2.0 export state.
@Alexanderamiri Alexanderamiri force-pushed the fix/cur-billing-view-arn branch from 3220f18 to a1edd18 Compare March 27, 2026 15:41
auto-merge was automatically disabled March 27, 2026 15:50

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant