Skip to content

Replace boundary resource with data source in platform#83

Merged
Alexanderamiri merged 1 commit into
mainfrom
refactor/boundary-data-source
Mar 17, 2026
Merged

Replace boundary resource with data source in platform#83
Alexanderamiri merged 1 commit into
mainfrom
refactor/boundary-data-source

Conversation

@Alexanderamiri
Copy link
Copy Markdown
Member

Summary

Completes the boundary migration from #82. The state migration has been done manually:

  1. Imported boundary into terraform/org/ state
  2. Removed from terraform/platform/ state via terraform state rm

This PR replaces the resource with a data.aws_iam_policy data source so platform CI reads the existing boundary policy instead of trying to recreate it.

All references updated: aws_iam_policy.developer_boundary.arndata.aws_iam_policy.developer_boundary.arn

Test plan

  • CI plan shows 1 resource removed (the boundary) and data source read — no destroy
  • All roles still reference the boundary ARN correctly
  • Future boundary changes go through terraform/org/ (human-applied)

The boundary resource was moved to terraform/org/ in #82 and the state
migration is complete (import to org state + state rm from platform).
Replace the resource with a data source so CI reads the existing policy
instead of trying to recreate it.
@Alexanderamiri Alexanderamiri enabled auto-merge (squash) March 17, 2026 21:36
@github-actions
Copy link
Copy Markdown

Terraform Plan

No changes — infrastructure is up to date.

Plan output

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

@Alexanderamiri Alexanderamiri merged commit a7c13e8 into main Mar 17, 2026
3 checks passed
@Alexanderamiri Alexanderamiri deleted the refactor/boundary-data-source branch March 17, 2026 21:36
Alexanderamiri added a commit that referenced this pull request May 9, 2026
## Summary

Completes the boundary migration from #82. The state migration has been
done manually:

1. Imported boundary into `terraform/org/` state
2. Removed from `terraform/platform/` state via `terraform state rm`

This PR replaces the resource with a `data.aws_iam_policy` data source
so platform CI reads the existing boundary policy instead of trying to
recreate it.

All references updated: `aws_iam_policy.developer_boundary.arn` →
`data.aws_iam_policy.developer_boundary.arn`

## Test plan
- [ ] CI plan shows 1 resource removed (the boundary) and data source
read — no destroy
- [ ] All roles still reference the boundary ARN correctly
- [ ] Future boundary changes go through `terraform/org/`
(human-applied)
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