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

[Choreo] Implementations for burst controlling support with subscription policies #3523

Merged
merged 5 commits into from
May 29, 2024

Conversation

slahirucd7
Copy link
Contributor

@slahirucd7 slahirucd7 commented May 21, 2024

Purpose

$subject
Related issue: https://github.com/wso2-enterprise/choreo/issues/28599

Issues

Fixes #

Automation tests

  • Unit tests added: No
  • Integration tests added: 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)

@slahirucd7 slahirucd7 added Type/Task Choreo java Pull requests that update Java code go Pull requests that update Go code labels May 21, 2024
Name: subscriptionPolicyEvent.PolicyName, QuotaType: subscriptionPolicyEvent.QuotaType,
subscriptionPolicy := types.SubscriptionPolicy{
ID: subscriptionPolicyEvent.PolicyID,
TenantID: TenantID,
Copy link
Contributor

Choose a reason for hiding this comment

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

We can remove TenantID from CC. Are we processing it?
@malinthaprasan wdyt?

Choose a reason for hiding this comment

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

TenantId will always be -1234 (super tenant) in Choreo. In some cases I have seen it's 0 in some variables when it's not set properly. Anyway there's no use case to process the tenant ID in Choreo. If we can remove it without breaking the code, +1 to do it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Check how tenant ID parsed in other event types ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Checked during the PR review.

@malinthaprasan
Copy link

@renuka-fernando @slahirucd7
Shall we have a quick review for this via a call? Just wanted to understand how the data structures are kept etc.

minor improvements

changes for review suggestions

changes for review suggestions
@slahirucd7 slahirucd7 merged commit 7b16481 into wso2:choreo May 29, 2024
3 checks passed
@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

[succeeded] : dev-deployment-v2 : 20240529.22

@choreo-cicd
Copy link

[succeeded] Controlplane cluster : dev-deployment-v2 : 20240529.22

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

[succeeded] Dataplane(CDP2-WU2) cluster : stage-deployment-v2 : 20240530.3

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

[] Dataplane(CDP2-WU2) cluster : stage-deployment-v2 : 20240530.6

@choreo-cicd
Copy link

[failed] Controlplane cluster : prod-deployment-v2 : 20240531.3

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

[succeeded] Controlplane cluster : prod-deployment-v2 : 20240531.3

@choreo-cicd
Copy link

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

@choreo-cicd
Copy link

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

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

Successfully merging this pull request may close these issues.

5 participants