chore(deps): update terraform cloudposse/elasticsearch/aws to v0.44.0 - abandoned #51

There is an error when we try to create a domain without providing dedicated_master_count and dedicated_master_type even when the dedicated_master_enabled=false

references

closes #143

`v0.41.0`

Compare Source

Add option to apply security groups to domain @bgottlob (#134)

what

Adds capability to attach existing security groups to ElasticSearch domain by setting var.create_security_group to false
Preserves default behavior of creating a new security group with one rule for each item in var.security_groups

why

Some users expect var.security_groups to be a list of security groups to be directly attached to the ElasticSearch domain

references

Resolves #62

`v0.40.0`

Compare Source

Update README: change zone_awareness_enabled to bool @Zaargh (#142)

what

In the example use zone_awareness_enabled is passed to the module as string, when bool is expected.
Changed to bool.

why

Consistency.

`v0.39.1`

Compare Source

🤖 Automatic Updates

chore(deps): update terraform cloudposse/route53-cluster-hostname/aws to v0.12.3 @renovate (#152)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	module	patch	`0.12.2` -> `0.12.3`

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

`v0.12.3`

Compare Source

Add zone inputs, update tests, add usage @nitrocode (#42)

what

Add zone inputs, update tests, add usage

why

Verify zone name exists
Dynamically retrieve zone name based on data source inputs

references

git.io->cloudposse.tools update @dylanbannon (#40)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

DEV-143

`v0.39.0`

Compare Source

Add cold storage support @dm3ch (#148)

what

Add support of configuring cluster_config.cold_storage_options.enabled

why

Allows enabling support of cold storage

`v0.38.0`

Compare Source

Support ebs_throughput to enable using of gp3 @dm3ch (#150)

what

Support ebs volume thoughtput option

why

Cause documentation says that this option is required for gp3 volume type

references

`v0.37.0`

Compare Source

Added AutoTune support @dm3ch (#149)

what

Add support for AutoTune

why

Provide support of AutoTune feature

references

closes #121

`v0.36.0`

Compare Source

Update go.sum terratest version `0.31.4` @goruha (#151)

what

Update go.sum terratest version

why

Fix tests

git.io->cloudposse.tools update @dylanbannon (#133)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

DEV-143

`v0.35.1`

Compare Source

🚀 Enhancements

fix when awareness is disabled, always changing @sanarena (#123)

what

When we disable zone awareness, Terraform want to put in availability_zone_count on every single run,
so resource is always marked as changed.
This pull request fix this issue.

why

Avoid unnecessary AWS calls and changes.

`v0.35.0`

Compare Source

feat: add validation to availability_zone_count @morremeyer (#122)

what

This ensures that availability_zone_count is only set to allowed values, see https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elasticsearch_domain#availability_zone_count.

why

Without this change, it’s possible to set zone_awareness_enabled to true which will automatically use 2 AZs, but set availability_zone_count to 1, which is confusing

references

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elasticsearch_domain#availability_zone_count.

`v0.34.1`

Compare Source

🚀 Enhancements

set security group lifecycle @lgiuliani-mwb (#119)

what

Added a lifecycle to the security group.

why

While importing an existing resource-set to this module, if the SG had a different name, it will try to destroy the security group while attached to the cluster instances. The lifecycle optin will first create a new one, apply the change to the cluster and then destroy the unused SG.

references

AWS doesn't allow security group to be renamed, Terraform will try to destroy and re-create it, it won't catch the error but will timeout trying to destroy a security group with attached interfaces.

`v0.34.0`

Compare Source

cein/feature/add-iam-permissions-boundary-input @Cein-Markey (#120)

what

Add new iam_role_permissions_boundary variable with a default of empty string and place it in aws_iam_role.elasticsearch_user.permissions_boundary

why

This change is to allow users of the API to leverage/set permissions boundaries: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html

"A permissions boundary is an advanced feature for using a managed policy to set the maximum permissions that an identity-based policy can grant to an IAM entity"

`v0.33.3`

Compare Source

🤖 Automatic Updates

chore(deps): update terraform cloudposse/route53-cluster-hostname/aws to v0.12.2 @renovate (#115)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	module	patch	`0.12.0` -> `0.12.2`

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

`v0.12.2`

Compare Source

🚀 Enhancements

Bump AWS provider 3.0 @nitrocode (#36)

what

Bump AWS provider 3.0

why

Downstream modules can take advantage of the more recent aws provider

references

N/A

`v0.12.1`

Compare Source

🚀 Enhancements

Chore: run `make github/init` @korenyoni (#37)

what

Run make github/init.

why

Updates GHA-workflow-related files to their latest distribution.
The old context.tf distribution is incompatible with the tenant label.

references

https://github.com/cloudposse/terraform-null-label/releases/tag/0.25.0

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

`v0.33.2`

Compare Source

🤖 Automatic Updates

chore(deps): update terraform cloudposse/label/null to v0.25.0 @renovate (#116)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	module	minor	`0.24.1` -> `0.25.0`

Release Notes

cloudposse/terraform-null-label

`v0.25.0`

Compare Source

Add "tenant", "labels_as_tags", and "descriptors" @Nuru (#132)

what

Add additional label and id component: tenant
New input labels_as_tags controls which labels are exported as tags
New input descriptor_formats generates new output descriptors
Update README, remove link to obsolete terraform-terraform-label

why

Support users that host resources on behalf of and/or dedicated to single customers
Supersedes and closes #131, giving people control over which tags the module generates
Simple mechanism for creating multiple identifiers from the same inputs, reducing the need to create multiple instances of null-label
Document tenant, labels_as_tags, descriptor_formats, add additional clarification, stop promoting obsolete module

Fix: Update README Snippets @korenyoni (#130)

what

Update README snippets to reflect use of Terraform Registry.

why

Including snippets that reflect use of the Terraform Registry make it easier for users to quickly instantiate a null_label module.
README is out of date and does not include snippets that reflect use of the Terraform Registry.

references

N/A

Bridgecrew compliance @Nuru (#125)

what

Resolve Bridgecrew compliance complaint about example Autoscaling Group (BC_AWS_GENERAL_31)
Fix typo in README
Include Terraform lock file in .gitignore

why

Get clean Bridgecrew badge
Correct confusing error
Ensure lock files are not checked into GitHub

note

The PR can and should be merged into master to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging to master will update the README and badges, so is worthwhile, and the changes will move forward into the next release.

Properly output descriptors of chained modules @Nuru (#133)

what

Properly output descriptors of chained modules

why

Bug fix; implement intended behavior

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

`v0.33.1`

Compare Source

🤖 Automatic Updates

Update context.tf @cloudpossebot (#113)

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.33.0`

Compare Source

Remove unused template provider @kevcube (#109)

what

Remove deprecated and unused template plugin

why

This provider wasn't being used at all, and a build isn't provided for darwin-arm64, so it broke usage of this module on that platform

references

Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
Use closes #123, if this PR closes a GitHub issue #123

`v0.32.0`

Compare Source

Add a default for kibana_subdomain name @DavidWittman (#104)

Closes #82

what

Set the default for kibana_subdomain_name to be ""

why

Plans fail when this is not defined
This value isn't required, it defaults to module.kibana_label.id
elasticsearch_subdomain_name has a default as well

references

Closes #82

`v0.31.0`

Compare Source

feat: support custom enpoint configuration @gberenice (#105)

what

Adds support for ES custom endpoints since it was shipped in provider in v0.35

why

This helps to get rid of workaround like using null_resource to enable custom endpoint

references

https://github.com/hashicorp/terraform-provider-aws/pull/16192#event-4537309082

`v0.30.0`

Compare Source

No changes

`v0.29.1`

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/label/null to v0.24.1 @renovate (#100)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	terraform	minor	`0.22.1` -> `0.24.1`

Release Notes

cloudposse/terraform-null-label

`v0.24.1`

Compare Source

Allow control of letter case of outputs @SweetOps (#107)

You now have control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.

Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.

You can set label_key_case to one of upper, lower, or title, which will result in generated tag names in the corresponding case: NAME, name, or Name. For backwards compatibility, title is the default
You can set label_value_case to one of upper, lower, title, or none, which will result in output label values in the corresponding case (with none meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag values and in the id string.

You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.

One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".

Include updates to exports/context.tf @Nuru (#122 and #123)

what

Include updates to exports/context.tf
Update README with features and compatibilty
Add validation for id_length_limit

why

The exports/context.tf is what gets distributed and needs to be in sync
Replace outdated information
Was not validated earlier because validators are not supported in TF 0.12 but now we are dropping support for TF 0.12 and so we can add validators

Restore backward compatibility with v0.22.1 and earlier @Nuru (#121)

what

Restore backward compatibility with v0.22.1 and earlier
Allow setting of label_key_case and label_value_case by vars, not just by context attributes.

why

Allow interoperability of old and new modules
Normally, root modules make settings via individual variables, not by setting an entire context block.

Incorporates and closes #120

`v0.24.0`

Compare Source

Restore backward compatibility with v0.22.1 and earlier @Nuru (#121)

what

Restore backward compatibility with v0.22.1 and earlier
Allow setting of label_key_case and label_value_case by vars, not just by context attributes.

why

Allow interoperability of old and new modules
Normally, root modules make settings via individual variables, not by setting an entire context block.

Incorporates and closes #120

Allow control of letter case of outputs @SweetOps (#107)

You now have control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.

Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.

You can set label_key_case to one of upper, lower, or title, which will result in generated tag names in the corresponding case: NAME, name, or Name. For backwards compatibility, title is the default
You can set label_value_case to one of upper, lower, title, or none, which will result in output label values in the corresponding case (with none meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag values and in the id string.

You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.

One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".

Known issues

exports/context.tf still not backwards compatible
Validation for id_length not included in exports/context.tf

`v0.23.0`

Compare Source

Known issues

Does not interoperate with earlier versions of null-label. The canonical context = module.this.context fails if module.this.context is an older version
context.tf does not incorporate var.label_key_case and var.label_value_case into the module.this object, preventing those variables from taking effect in the root module's module.this.

feat: add support for setting letter case of context tags @SweetOps (#107)

With this release, you gain control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.

Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.

You can set label_key_case to one of upper, lower, or title, which will result in generated tag names in the corresponding case: NAME, name, or Name. For backwards compatibility, title is the default
You can set label_value_case to one of upper, lower, title, or none, which will result in output label values in the corresponding case (with none meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag values and in the id string.

You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.

One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".

Update Terraform cloudposse/route53-cluster-hostname/aws to v0.12.0 @renovate (#101)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	terraform	minor	`0.10.0` -> `0.12.0`

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

`v0.12.0`

Compare Source

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

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

`v0.11.0`

Compare Source

minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#34)

what

update context.tf to v0.23.0
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
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

`v0.10.1`

Compare Source

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#33)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

`v0.29.0`

Compare Source

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

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

`v0.28.1`

Compare Source

🤖 Automatic Updates

Update context.tf @cloudpossebot (#99)

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.28.0`

Compare Source

minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#97)

what

update context.tf to v0.23.0
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
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

`v0.27.0`

Compare Source

domain_endpoint_options_enforce_https enabled by default @maximmi (#95)

what

BridgeCrew compliance checks fix
readme updated
default behaviour changed: Elasticsearch Domain EnforceHTTPS enabled by default

why

To be able to position our modules as standards compliant
stay in sync with code
To comply BridgeCrew check

references

https://docs.bridgecrew.io/docs/elasticsearch_6

`v0.26.0`

Compare Source

Terraform 0.14 upgrade @maximmi (#90)

what

Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

Support Terraform 0.14

`v0.25.1`

Compare Source

🚀 Enhancements

Bump dependencies to support v14 @svrakitin (#88)

Bumped versions to eliminate following errors on v0.14.x:

Error: Unsupported Terraform Core version

  on xxx, in terraform:
   2:   required_version = ">= 0.12.0, < 0.14.0"

`v0.25.0`

Compare Source

[GH Issue 85] Support Audit Logging @neuroticnetworks (#86)

what

This PR enables AUDIT_LOGS support in the CloudPosse ES Module.

why

There are currently four types of logs supported by Terraform Elasticsearch: INDEX_SLOW_LOGS, SEARCH_SLOW_LOGS, ES_APPLICATION_LOGS, and AUDIT_LOGS (xref log_publishing_options here) The CloudPosse module currently supports the first of these log types, but does not allow you to enable AUDIT_LOGS.

references

closes #85
closes #84

`v0.24.1`

Compare Source

🐛 Bug Fixes

Remove SID from ES access policy @Nuru (#76)

what

Remove SID from ES access policy

why

SID is accepted but not stored, causing perpetual drift in Terraform plan

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate · 2023-07-19T17:59:02Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

renovate · 2023-07-20T03:25:41Z

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

chore(deps): update terraform cloudposse/elasticsearch/aws to v0.44.0

b2ef2ff

renovate bot requested review from a team as code owners July 19, 2023 17:50

renovate bot requested review from dotCipher and woz5999 July 19, 2023 17:50

renovate bot added the auto-update This PR was automatically generated label Jul 19, 2023

Auto-update README.md

9ee5f9c

renovate bot changed the title ~~chore(deps): update terraform cloudposse/elasticsearch/aws to v0.44.0~~ chore(deps): update terraform cloudposse/elasticsearch/aws to v0.44.0 - abandoned Jul 20, 2023

hans-d closed this Mar 2, 2024

Uh oh!

chore(deps): update terraform cloudposse/elasticsearch/aws to v0.44.0 - abandoned #51

chore(deps): update terraform cloudposse/elasticsearch/aws to v0.44.0 - abandoned #51

Uh oh!

Conversation

renovate bot commented Jul 19, 2023

Release Notes

what

why

references

what

why

references

what

why

references

what

why

🤖 Automatic Updates

Release Notes

what

why

references

what and why

References

what

why

what

why

references

what

why

references

what

why

what and why

References

🚀 Enhancements

what

why

what

why

references

🚀 Enhancements

what

why

references

what

why

🤖 Automatic Updates

Release Notes

🚀 Enhancements

what

why

references

🚀 Enhancements

what

why

references

Configuration

🤖 Automatic Updates

Release Notes

what

why

what

why

references

what

why

note

what

why

Configuration

🤖 Automatic Updates

what

why

what

why

references

what