Skip to content

Conversation

@vivian12300
Copy link
Contributor

This updates the feature flag schema to store the default value of the flag.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@github-actions github-actions bot added the p2 label Jul 28, 2025
@aws-cdk-automation aws-cdk-automation requested a review from a team July 28, 2025 15:03
@codecov-commenter
Copy link

codecov-commenter commented Jul 28, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.58%. Comparing base (969c499) to head (ba204b6).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #742      +/-   ##
==========================================
- Coverage   81.16%   80.58%   -0.59%     
==========================================
  Files          61       61              
  Lines        8267     8267              
  Branches      953      946       -7     
==========================================
- Hits         6710     6662      -48     
- Misses       1529     1580      +51     
+ Partials       28       25       -3     
Flag Coverage Δ
suite.unit 80.58% <ø> (-0.59%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@aws-cdk-automation aws-cdk-automation added this pull request to the merge queue Jul 28, 2025
Merged via the queue into aws:main with commit 45ceb89 Jul 28, 2025
27 checks passed
rix0rrr added a commit to aws/aws-cdk that referenced this pull request Aug 12, 2025
…ry versions

This change goes together with
aws/aws-cdk-cli#782, to undo some decisions made
in https://github.com/aws/aws-cdk/pull/35108/files and
aws/aws-cdk-cli#742.

We used to store `unconfiguredBehavesLike` values for both `v1` and `v2`
(and `v3`, `v4`, etc) into the feature flag report, but we only needed to
store the value for the *current* library version. We are now defining
the "v2" field to hold the current version information, and are updating
the feature flag generation code to not emit `v1` data, and stay correct
if we ever start releasing `v3`.
mergify bot pushed a commit to aws/aws-cdk that referenced this pull request Aug 12, 2025
…ry versions (#35215)

This change goes together with
aws/aws-cdk-cli#782, to undo some decisions made in https://github.com/aws/aws-cdk/pull/35108/files and aws/aws-cdk-cli#742.

We used to store `unconfiguredBehavesLike` values for both `v1` and `v2` (and `v3`, `v4`, etc) into the feature flag report, but we only needed to store the value for the *current* library version. We are now defining the "v2" field to hold the current version information, and are updating the feature flag generation code to not emit `v1` data, and stay correct if we ever start releasing `v3`.

This is labeled as a `chore` and not a `fix` because it doesn't really fix user-visible behavior.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@vivian12300 vivian12300 deleted the change-feature-flag-schema branch August 12, 2025 17:08
djglaser pushed a commit to djglaser/aws-cdk that referenced this pull request Aug 13, 2025
…ry versions (aws#35215)

This change goes together with
aws/aws-cdk-cli#782, to undo some decisions made in https://github.com/aws/aws-cdk/pull/35108/files and aws/aws-cdk-cli#742.

We used to store `unconfiguredBehavesLike` values for both `v1` and `v2` (and `v3`, `v4`, etc) into the feature flag report, but we only needed to store the value for the *current* library version. We are now defining the "v2" field to hold the current version information, and are updating the feature flag generation code to not emit `v1` data, and stay correct if we ever start releasing `v3`.

This is labeled as a `chore` and not a `fix` because it doesn't really fix user-visible behavior.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
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.

4 participants