Rupa Lahiri

Hi, I am new to this repo, can you give guidance on how this issue can be fixed? In create_title, should the slug be validated before creating the Title object?

@eirsep Would it be better to derive the trigger types from a list of monitor types? Is that rest API endpoint already available?

Can we add: Object Oriented Programming helps us to keep data and the functions which will handle the data together. We need to keep in mind a class keeps related...

Please see if the comments from an issue from terraform repository helps https://github.com/hashicorp/terraform/issues/31769#issuecomment-1243911229 https://github.com/hashicorp/terraform/issues/31769#issuecomment-1243987954

The attribute needs the same value for plan phase and apply phase, hence the error.

Further reference from https://github.com/hashicorp/terraform/issues/25090 : The general rule underlying that error is that if the plan for a particular attribute has a known value (anything other than "known after apply")...

When there are no documents present in the index, updating the index mapping through terraform code works as expected. The index mapping is updated successfully. Using the following terraform code,...

aws_dynamodb_table resource recommends using lifecycle ignore_changes for some arguments in certain situations https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/dynamodb_table

@uriofferup Are you willing to try https://github.com/opensearch-project/opensearch-go/blob/main/guides/json.md

@sharathganga @prudhvigodithi once the rollover happens, the index created using terraform will no longer have is_write_index true, using plan and apply again will throw the more than one write index...