Skip to content

Conversation

@rajiv-jain-netapp
Copy link

@rajiv-jain-netapp rajiv-jain-netapp commented Oct 13, 2025

Description

This PR...

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

<artifactId>cloud-engine-storage-volume</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we need this?

Copy link
Author

Choose a reason for hiding this comment

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

for now yes, we can remove it later if required.

<dependency>
<groupId>org.json</groupId>
<artifactId>json</artifactId>
<version>20230227</version>

Choose a reason for hiding this comment

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

It is better to keep version under properties tag as it is easy to maintain. Same is applicable for other dependencies

Copy link
Author

Choose a reason for hiding this comment

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

done

private List<AggregateDTO> aggregates;
private SvmDTO svm;

// getters and setters

Choose a reason for hiding this comment

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

Please use @Getter/ @Setter annotation or @DaTa annotation to remove these getters/setters

Copy link
Author

Choose a reason for hiding this comment

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

I am trying to keep dependencies less. Hence prefer to write getter and setter manually

Choose a reason for hiding this comment

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

There is one caveat with @DaTa , it writes its own equals and hashcode method by comparing all fields of object which we dont want sometimes.


public static class Job {
private String uuid;
private Links links;
Copy link

@suryag1201 suryag1201 Oct 13, 2025

Choose a reason for hiding this comment

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

same here, use @DaTa annotation for other classes also

Copy link
Author

Choose a reason for hiding this comment

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

Same as above response

public void setName(String name) { this.name = name; }
}

public static class SvmDTO {

Choose a reason for hiding this comment

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

we should keep this DTO outside bcz it can be reusable by other DTOs also

Copy link
Author

Choose a reason for hiding this comment

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

I thought of keeping them inside for now and taking them out case by case. That way, we can keep the count of files lower. The number of files is already shooting up.

Copy link
Author

@rajiv-jain-netapp rajiv-jain-netapp left a comment

Choose a reason for hiding this comment

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

responded on the comments, reposting the changes with the new changes as per comments

<properties>
<spring-cloud.version>2021.0.7</spring-cloud.version>
<openfeign.version>11.0</openfeign.version>
</properties>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Need to include both spring-web and spring-boot-starter(v2.7.10), if we intend to use @FeignClient annotation in VolumeFeignClient.java

Copy link
Author

Choose a reason for hiding this comment

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

As mentioned earlier, I don't see any compilation issues with the newly added code. If additional dependencies are required as we proceed, we can incorporate them accordingly. For now, I'd prefer not to include all potential dependencies until the corresponding code is in place.

Copy link
Author

@rajiv-jain-netapp rajiv-jain-netapp left a comment

Choose a reason for hiding this comment

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

reverted to the comments

@rajiv-jain-netapp rajiv-jain-netapp merged commit 2822946 into main Oct 14, 2025
16 checks passed
@JsonInclude(JsonInclude.Include.NON_NULL)
public class Aggregate {

@SerializedName("name")

Choose a reason for hiding this comment

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

I see in some model we are using JsonProperty and SerializedName which serves same purpose but are from 2 different libraries. What's your thought on using Jackson or gson any one of the above across our models.

private List<AggregateDTO> aggregates;
private SvmDTO svm;

// getters and setters

Choose a reason for hiding this comment

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

There is one caveat with @DaTa , it writes its own equals and hashcode method by comparing all fields of object which we dont want sometimes.

sandeeplocharla pushed a commit that referenced this pull request Oct 21, 2025
…ommits.

# This is the 1st commit message:

CSTACKEX-25: Basic class structure

# This is the commit message #2:

Add PrimaryStoragePool base code

# This is the commit message #3:

CSTACKEX-25: Create Volume code basic code added

# This is the commit message #4:

CSTACKEX-25: additional logic for Primary storage pool creation

# This is the commit message #5:

CSTACKEX-29 Cluster, SVM and Aggr Feign Client

# This is the commit message #6:

CSTACKEX-29 Added License Info

# This is the commit message #7:

CSTACKEX-29 Resolve Review Comments

# This is the commit message #8:

CSTACKEX-29 Resolve Style check issues

� This is the commit message #9:

CSTACKEX-29 Resolve Style check issues

� This is the commit message #10:

CSTACKEX-29 Resolve Precommits Issues

# This is the commit message #11:

CSTACKEX-29 Resolve Precommits Issues
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