v0.16.0

Add support to config module for on-call schedules (and some other fixes) @danjbh (#30)

what

• Update Github Actions
• Adding support for schedules and schedule_rotations to config module
• Updating config module README.md
• Adding support for multiple rules to config module escalations
• Resolves issue w/ team routing rules criteria
• Resolves issue w/ team member sorting (or lack thereof)
• Modifying for_each logic in config module to fix issue w/ mismatch between object schemas
• Removing unsupported resources from complete example (fixes terratest failure)

why

• We must have support for on-call schedules & rotations in the config module!

v0.15.0

Module `schedule` @Benbentwo (#28)

what

• Add a TF schedule module

why

• The terraform schedule module will be used to create and manage on-call schedules

references

• https://support.atlassian.com/opsgenie/docs/manage-on-call-schedules-and-rotations/
• https://www.atlassian.com/software/opsgenie/on-call-management-and-escalations
• https://support.atlassian.com/opsgenie/docs/build-an-on-call-schedule/

v0.14.5

🚀 Enhancements

`time_restriction` support to `team_routing_rule` @Benbentwo (#27)

what

• Adds Time_Restriction to team_routing_rule

why

• Follow the sun model requires this

references

• Github Issue #282

v0.14.4

🚀 Enhancements

Allow for configuring webhook_url for api_integrations @clausa (#23)

what

• Allow for configuring webhook_url for api_integrations

why

• The webhook_url parameter is required when type is Webhook API integration

v0.14.3

🚀 Enhancements

Update context.tfs to v 0.25.0 @Benbentwo (#26)

what

• Updates all contexts.tf to latest

v0.14.2

🤖 Automatic Updates

Update context.tf @cloudpossebot (#24)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.14.1

🚀 Enhancements

Change for_each to avoid nested maps typing_error @nate-selzer (#22)

what

• Fix conditional operator

why

• Prevent terraform errors like

Error: Inconsistent conditional result types

  on .terraform/modules/opsgenie_config/modules/config/integration_actions.tf line 2, in resource "opsgenie_integration_action" "this":
   2:   for_each = module.this.enabled ? { for integration_action in local.integration_actions : integration_action.name => integration_action } : {}
    |----------------
    | local.integration_actions is tuple with 14 elements
    | module.this.enabled is true

The true and false result expressions must have consistent types. The given
expressions are object and object, respectively.

references

• https://stackoverflow.com/questions/66970542/inconsistent-conditional-result-types-with-locals-templatization

v0.14.0

Feat: Add Support for Integration Actions @korenyoni (#20)

what

• Add support for the opsgenie_integration_action resource in both its own submodule and the config submodule.
• update context.tf in example configs

why

• The opsgenie_integration_action is useful for manipulating alerts in ways that are not possible with opsgenie_alert_policy and opsgenie_notification_policy

references

• https://registry.terraform.io/providers/opsgenie/opsgenie/latest/docs/resources/integration_action

v0.13.0

Feat/Fix: Ensure all Modules Adhere module.this.enabled; Update context.tf in all Submodules; Update Documentation Snippets @korenyoni (#19)

what

• Add context.tf to all submodules
• Update context.tf in all submodules
• Ensure all resources adhere module.this.enabled
• Update all READMEs to use Terraform registry as source instead of git
• Update root-level README copyright year and contributors.

why

• Adding the same version of context.tf in all submodules and root-level is more consistent and won't result in version issues stemming from null_label module in context.tf
• Ensuring all modules adhere module.this.enabled is more consistent
• Ensuring module snippets in documentation are using the Terraform registry means we are showing users the up-to-date way of instantiating modules

references

• N/A

v0.12.0

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#18)

what

• update context.tf to v0.24.1
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant