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

Please add ‘notification_configuration’(?) resource #68

Closed
hagurganus opened this issue Mar 7, 2019 · 6 comments · Fixed by #86
Closed

Please add ‘notification_configuration’(?) resource #68

hagurganus opened this issue Mar 7, 2019 · 6 comments · Fixed by #86
Assignees

Comments

@hagurganus
Copy link
Contributor

hagurganus commented Mar 7, 2019

With the release of the notifications feature for TFE on 3/1, and the corresponding Notification Configurations API, it’d be nice to see that added as a resource in the TFE provider.

I may endeavor to do this myself, but I thought I’d add a ‘feature request’ here in the Issues tracker in case anyone else is considering doing the same work.

@svanharmelen
Copy link
Contributor

Thanks for reaching out @hagurganus! We are working on adding support for notifications, so it will be added to the provider in an upcoming release.

@v6
Copy link

v6 commented Apr 22, 2019

For now, would you recommend to use a null resource and comment with a link to this GH issue?

@enriquerecarte
Copy link

Hi @svanharmelen is there an estimate on when the next release could be? Would be really good to manage the notifications in terraform.

@svanharmelen
Copy link
Contributor

I think we should divert that question to @caseylang as he is the one currently working on this. So @caseylang any estimate for when this will be added to the provider? Thanks!

@caseylang
Copy link

Hi there! This is scheduled to be added in July. Apologies for the delay!

@hagurganus
Copy link
Contributor Author

hagurganus commented Aug 19, 2019 via email

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

Successfully merging a pull request may close this issue.

6 participants