-
Notifications
You must be signed in to change notification settings - Fork 151
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
[WIP] r/policy_set: add support for VCS policy sets #80
Conversation
Depends on hashicorp/go-tfe#77. |
2648d59
to
caa666c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks right to me 👍 will probably want @chrisarcand's review too once he's back!
07a60ea
to
7e6fc50
Compare
This adds the necessary changes to allow for VCS policy sets. VCS-backed policy sets are defined by supplying the vcs_repo - and optionally, policies_path, arguments to the tfe_policy_set resource. This is in lieu of policy_ids. Changing either vcs_repo or policies_path will result in a new resource being forced.
7e6fc50
to
e1994da
Compare
I think the changes here should comprise most of the final changes necessary to put this through. @svanharmelen I'd still like to hear your thoughts/response of the ordering of the options. I'll defer to your judgement here. |
@vancluever I made a few small changes to make sure all logic is consistent (mainly the tests). It would be great if you could review and run the tests one more time to make sure they all pass. If they do, this should be good to be merged and released 👍 |
Looks good, this all passes. I will be merging shortly! |
This adds the necessary changes to allow for VCS policy sets.
VCS-backed policy sets are defined by supplying the vcs_repo - and
optionally, policies_path, arguments to the tfe_policy_set resource.
This is in lieu of policy_ids.
Changing either vcs_repo or policies_path will result in a new
resource being forced.