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

[AV-87721] GSI release documentation for Terraform V1.4.0 #244

Open
wants to merge 58 commits into
base: AV-87721_release_documentation_for_V1.4.0
Choose a base branch
from

Conversation

a-atri
Copy link
Collaborator

@a-atri a-atri commented Nov 21, 2024

Jira

  • AV-87721

Description

Release documentation of GSI for terraform version V1.4.0

Type of Change

  • Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
  • New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR.
  • Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR.
  • This change requires a documentation update
  • Documentation fix/enhancement

Manual Testing Approach

How was this change tested and do you have evidence? (REQUIRED: Select at least 1)

  • Manually tested
  • Unit tested
  • Acceptance tested
  • Unable to test / will not test (Please provide comments in section below)

Testing

Testing

Required Checklist:

  • I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
  • I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
  • I have added any necessary documentation (if required)
  • I have run make fmt and formatted my code
  • I have made sure that no schema field is marked with both requiresReplace and computed

Further comments

@a-atri a-atri requested review from a team as code owners November 21, 2024 09:49
Copy link

@simon-dew simon-dew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few comments

docs/guides/1.4.0-upgrade-guide.md Outdated Show resolved Hide resolved
docs/guides/1.4.0-upgrade-guide.md Outdated Show resolved Hide resolved

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See also comments in #243

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments in #243 . The following comments apply here also:

  1. The top few entries in this list have more description under the link. The later entries, including these two, just repeat the link title. Could expand the descriptions for later entries including these two. Little point in just repeating the link title text.

  2. The top few entries in this list have a colon (:) after the link. For consistency, either remove the colon from the top few entries or add a colon to all subsequent entries, including these two.


This example shows how to create secondary indexes on a Capella cluster.

This creates 5 deferred indexes in test.test.test. Deferred indexes are best suited for large indexes, or when creating many indexes.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe spell it out?

Suggested change
This creates 5 deferred indexes in test.test.test. Deferred indexes are best suited for large indexes, or when creating many indexes.
This creates 5 deferred indexes in a collection called `test`, which is located in a scope called `test` within a bucket also called `test`. Deferred indexes are best suited for large indexes, or when creating many indexes.

Copy link
Contributor

@rajagp rajagp Nov 21, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In addition to what Simon indicated - which is providing the clarify - I though we had discussed this previously and we we were going to use more meaningful names and not just test, test, test - at very laest "mybucket", "myscope" and "mycollection"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also many indexes to multiple indexes. (Essentially, since we can't give a number, we can leave it as plural)

examples/gsi/deferred/README.md Outdated Show resolved Hide resolved

This example shows how to create secondary indexes on a Capella cluster.

This creates 5 non-deferred indexes in test.test.test. Non-deferred indexes are best suited when creating small indexes.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, maybe spell it out?

Suggested change
This creates 5 non-deferred indexes in test.test.test. Non-deferred indexes are best suited when creating small indexes.
This creates 5 non-deferred indexes in a collection called `test`, which is located in a scope called `test` within a bucket also called `test`. Non-deferred indexes are best suited when creating small indexes.


This creates 5 non-deferred indexes in test.test.test. Non-deferred indexes are best suited when creating small indexes.

To run configure your Couchbase Capella provider as described in README in the root of this project.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To run configure your Couchbase Capella provider as described in README in the root of this project.
To try this example, configure your Couchbase Capella provider as described in README in the root of this project.

3. DELETE: Delete the indexes.
5. IMPORT: Import an index to the state file.

If you check the `terraform.template.tfvars` file - Make sure you copy the file to `terraform.tfvars` and update the values of the variables as per the correct organization access.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you check the `terraform.template.tfvars` file - Make sure you copy the file to `terraform.tfvars` and update the values of the variables as per the correct organization access.
Check the `terraform.template.tfvars` file. Make sure you copy the file to `terraform.tfvars` and update the values of the variables for your organization access.

Comment on lines +21 to +22
### Ensure you create indexes.json which is a file with indexes
### Place this file in the same directory as the terraform script.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As before, I don't like misusing the heading semantics just for emphasis.

Suggested change
### Ensure you create indexes.json which is a file with indexes
### Place this file in the same directory as the terraform script.
**Ensure you create `indexes.json`, which is a file with indexes.**
**Place this file in the same directory as the terraform script.**

@@ -306,3 +306,7 @@ To get started, see the [Provider Example Configs](https://github.com/couchbasec

Manage Flush Bucket

* [Manage GSI](https://github.com/couchbasecloud/terraform-provider-couchbase-capella/tree/main/examples/gsi)

Manage GSI
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@l0n3star Tagging in reference to discussion on slack thread. Tagging here so we don't miss

@@ -19,6 +19,7 @@ In this demo, we will perform the following operations:
15. Create a new audit log settings.
16. Enable private endpoint service on the cluster.
17. Create a new network peer.
18. Create an index.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What kind of index? GSI and deferred or non-deferred?

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

Successfully merging this pull request may close these issues.

5 participants