feat: add support for different types in email integration #467
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've tried to provision the integration of type "UptrendsEmail" which is mentioned here: https://support.atlassian.com/opsgenie/docs/integration-types-to-be-used-with-the-api/ . When I tried to provision it using opsgenie_api_integration resource with type "UptrendsEmail" I got an error saying: Error Detail: map[emailUsername:must not be blank] . So I've tried to use opsgenie_email_integration resource but it only creates an integration of type "Email" by default (cannot set to type "UptrendsEmail").
I've tried to update my email integration which had the specific owner team and it just got removed from my team.
Changes:
Looking forward to your review and thanks in advance :)