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

Use iam policy module instead of raw resources #80

Open
nitrocode opened this issue Nov 23, 2024 · 0 comments
Open

Use iam policy module instead of raw resources #80

nitrocode opened this issue Nov 23, 2024 · 0 comments

Comments

@nitrocode
Copy link
Member

Describe the Feature

To take advantage of the power of the iam_policy input of the iam policy module, it would be nice to dogfood that module within this module, use a migrations.tf here to migrate resources to the new address, and expose each of policy module's inputs here

Expected Behavior

Same behavior as upstream module without needing to reinvent the wheel

The inline policy resource should not be removed since the upstream module only supports managed policies by design

Use Case

Take advantage of upstream logic instead of recreating it

Describe Ideal Solution

See above

Alternatives Considered

No response

Additional Context

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

No branches or pull requests

1 participant