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

Adding insights data to metadataContext #3601

Merged
merged 3 commits into from
Oct 15, 2024
Merged

Adding insights data to metadataContext #3601

merged 3 commits into from
Oct 15, 2024

Conversation

ruks
Copy link
Contributor

@ruks ruks commented Oct 11, 2024

Purpose

  • Adding insights data to metadataContext

Issues

Fixes #

Automation tests

  • Unit tests added: Yes/No
  • Integration tests added: Yes/No

Tested environments

Not Tested


Maintainers: Check before merge

  • Assigned 'Type' label
  • Assigned the project
  • Validated respective github issues
  • Assigned milestone to the github issue(s)

@@ -146,6 +147,9 @@ public String init(Api api) {
api.getEndpointSecurity().getSandBoxSecurityInfo()));
}

org.wso2.choreo.connect.enforcer.commons.model.ChoreoComponentInfo choreoComponentInfo = getChoreoComponentInfo(
Copy link
Contributor

Choose a reason for hiding this comment

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

Shall we import the class

Copy link
Contributor Author

Choose a reason for hiding this comment

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

a class with the same name already imported. Hence had to improve with the fully qualified class name.


initFilters();
return basePath;
}

private static org.wso2.choreo.connect.enforcer.commons.model.ChoreoComponentInfo getChoreoComponentInfo(
Copy link
Contributor

Choose a reason for hiding this comment

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

same here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

a class with the same name already imported. Hence had to improve with the fully qualified class name.

@ruks ruks merged commit de31034 into wso2:choreo Oct 15, 2024
2 of 3 checks passed
@choreo-cicd
Copy link

[succeeded] Dataplane(EastUS) cluster : dev-deployment-v2 : 20241015.8

@choreo-cicd
Copy link

[succeeded] Dataplane(NorthEU) cluster : dev-deployment-v2 : 20241015.8

@choreo-cicd
Copy link

[succeeded] : dev-deployment-v2 : 20241015.8

@choreo-cicd
Copy link

[succeeded] Dataplane(NorthEU) cluster : stage-deployment-v2 : 20241017.1

@choreo-cicd
Copy link

[failed] Controlplane cluster : stage-deployment-v2 : 20241017.1

@choreo-cicd
Copy link

[failed] Dataplane(EastUS) cluster : stage-deployment-v2 : 20241017.1

@choreo-cicd
Copy link

[] Dataplane(EastUS) cluster : stage-deployment-v2 : 20241017.2

@choreo-cicd
Copy link

[] Dataplane(NorthEU) cluster : stage-deployment-v2 : 20241017.2

@choreo-cicd
Copy link

[] Controlplane cluster : stage-deployment-v2 : 20241017.2

@choreo-cicd
Copy link

[succeeded] Dataplane(NorthEU) cluster : stage-deployment-v2 : 20241017.4

@choreo-cicd
Copy link

[succeeded] Dataplane(EastUS) cluster : stage-deployment-v2 : 20241017.4

@choreo-cicd
Copy link

[failed] Controlplane cluster : stage-deployment-v2 : 20241017.4

@choreo-cicd
Copy link

[] Controlplane cluster : stage-deployment-v2 : 20241018.2

@choreo-cicd
Copy link

[] Dataplane(NorthEU) cluster : stage-deployment-v2 : 20241018.2

@choreo-cicd
Copy link

[] Dataplane(EastUS) cluster : stage-deployment-v2 : 20241018.2

@choreo-cicd
Copy link

[] Dataplane(EastUS) cluster : prod-deployment-v2 : 20241021.3

@choreo-cicd
Copy link

[] Controlplane cluster : prod-deployment-v2 : 20241021.3

@choreo-cicd
Copy link

[] Dataplane(NorthEU) cluster : prod-deployment-v2 : 20241021.3

@choreo-cicd
Copy link

[] Dataplane(CDP2-WU2) cluster : prod-deployment-v2 : 20241021.3

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

Successfully merging this pull request may close these issues.

3 participants