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

Assurance Policy resources should only accept possible values for their particular type #264

Open
rjulian opened this issue Mar 28, 2024 · 0 comments

Comments

@rjulian
Copy link
Contributor

rjulian commented Mar 28, 2024

Right now, the potential parameters for every assurance policy type is able to be passed into each assurance policy resource, even if those parameters aren't possible for the policy type. I understand that the API itself supports this, but for the purposes of usability of the TF module, we should limit the possible parameters to just those which apply.

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