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-86105] initialized autoexpansion field with null value #226

Conversation

aniket-Kumar-c
Copy link
Collaborator

@aniket-Kumar-c aniket-Kumar-c commented Sep 19, 2024

Jira

  • AV-86105

Description

Please include a summary of the fix/feature/change, including any relevant motivation and context.

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

@aniket-Kumar-c aniket-Kumar-c requested review from a team as code owners September 19, 2024 08:57
Copy link
Contributor

@PaulomeeCb PaulomeeCb left a comment

Choose a reason for hiding this comment

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

@aniket-Kumar-c thanks for the change, can you add some testing/ss to the PR or ticket please?

@aniket-Kumar-c
Copy link
Collaborator Author

@aniket-Kumar-c thanks for the change, can you add some testing/ss to the PR or ticket please?

http://172.23.121.80/job/terraform-test/729/

The above job ran on this branch. It seems some tests are still failing for the cluster due to the introduction of new guardrails on the compute type.

@aniket-Kumar-c aniket-Kumar-c merged commit b860a1f into main Sep 19, 2024
3 of 4 checks passed
Lagher0 added a commit that referenced this pull request Oct 6, 2024
…cket

* origin/main:
  AV-78889 - VNET peering azure (#216)
  Av 87139 fix gorunner version (#232)
  Av 87139 fix gorunner version (#231)
  Av 87139 fix gorunner version (#230)
  AV-87139 fix gorunner version (#229)
  Updating the version for gorunner (#228)
  AV-87077 | handle computed values in acc test (#227)
  [AV-86105] initialized autoexpansion field with null value (#226)
  [AV-86503] Updated the changelog (#221)
  [AV-86224] Generated docs for Terraform V1.3.0 (#220)
  [AV-86845] Deprecate the `configurationType` attribute in the cluster resource (#222)
  Bump github.com/hashicorp/terraform-plugin-go from 0.22.1 to 0.23.0 (#193)
  Bump github.com/hashicorp/terraform-plugin-framework from 1.6.1 to 1.9.0 (#201)
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.

4 participants