-
Notifications
You must be signed in to change notification settings - Fork 153
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
Enabled to configure the interval of livestate store for Lambda #5269
Conversation
Signed-off-by: t-kikuc <tkikuchi07f@gmail.com>
Signed-off-by: t-kikuc <tkikuchi07f@gmail.com>
pkg/config/piped.go
Outdated
// The interval to fetch the live state of Lambda functions. | ||
// Default is 15s. | ||
// To reduce AWS API calls, this interval should be larger. | ||
LiveStateInterval Duration `json:"liveStateInterval,omitempty" default:"15s"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about to make this general name like awsAPICallInterval
. Since we are going to migrate platform to plugin, I want to ensure less configuration update as possible in the mean time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think liveStateInterval
will not change while migrating to the plugin.
Plugin will change the name of the LiveState feature??
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I mean if we allow some name like this in the configuration, then we would have something like driftDetectionInterval
later, which I think should not be here (in the piped.platformProvider config). Livestate or Drift detection config should not be related directly to platform, is what I tried to explain. Name like awsAPICallInterval
is more relevant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, I want to ensure we do not add names/configs that will be changed too much later due to the migrating cost when the user moves to use the plugin-piped. That's why I said, I don't think the used name is good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I almost agree with @khanhtc1202 that we can name this configuration a generic word, but I think awsAPICallInterval is a bit confusing because it sounds like a rate-limiting feature.
We call AWS APIs in other functionality, such as deployment, and they are not affected by this configuration.
What about like awsAPIPollingInterval?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The name awsAPIPollingInterval
is lgtm 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@khanhtc1202 @Warashi
Thank you, I changed to awsAPIPollingInterval
Signed-off-by: t-kikuc <tkikuchi07f@gmail.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5269 +/- ##
==========================================
+ Coverage 24.08% 24.27% +0.18%
==========================================
Files 441 440 -1
Lines 47099 46754 -345
==========================================
+ Hits 11345 11348 +3
+ Misses 34850 34502 -348
Partials 904 904 ☔ View full report in Codecov by Sentry. |
Signed-off-by: t-kikuc <tkikuchi07f@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
* add liveStateInterval for Lambda Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> * add docs of liveStateInterval Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> * fix a test Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> * Rename to 'awsAPIPollingInterval' Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> --------- Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> Signed-off-by: pipecd-bot <pipecd.dev@gmail.com>
* Fix the workflow publishes quickstart manifests (#5266) * Add pull-requests permission to the workflow Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev> * Set the base branch to the default branch of the repository Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev> * Use `github.ref_name` to determine the version of manifests Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev> * Checkout master branch to make PR to master branch Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev> --------- Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev> Signed-off-by: pipecd-bot <pipecd.dev@gmail.com> * Remove pipectl quickstart command (#5268) * Remove pipectl quickstart command Signed-off-by: khanhtc1202 <khanhtc1202@gmail.com> * Remove the quickstart from docs Signed-off-by: khanhtc1202 <khanhtc1202@gmail.com> --------- Signed-off-by: khanhtc1202 <khanhtc1202@gmail.com> Signed-off-by: pipecd-bot <pipecd.dev@gmail.com> * Enabled to configure the interval of livestate store for Lambda (#5269) * add liveStateInterval for Lambda Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> * add docs of liveStateInterval Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> * fix a test Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> * Rename to 'awsAPIPollingInterval' Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> --------- Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> Signed-off-by: pipecd-bot <pipecd.dev@gmail.com> * Update RELEASE to v0.49.2 and sync docs of v0.49.x (#5272) Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> Signed-off-by: pipecd-bot <pipecd.dev@gmail.com> --------- Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev> Signed-off-by: pipecd-bot <pipecd.dev@gmail.com> Signed-off-by: khanhtc1202 <khanhtc1202@gmail.com> Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> Co-authored-by: Shinnosuke Sawada-Dazai <shin@warashi.dev> Co-authored-by: Khanh Tran <32532742+khanhtc1202@users.noreply.github.com> Co-authored-by: Tetsuya Kikuchi <97105818+t-kikuc@users.noreply.github.com>
What this PR does / why we need it:
What for:
Which issue(s) this PR fixes:
N/A
Does this PR introduce a user-facing change?: