revisit App APIs #1891
Assignees
Labels
@aws-cdk/core
Related to core CDK functionality
Comments
4 tasks
eladb
removed
the
package/awscl
eladb
pushed a commit
that referenced
this issue
Jun 3, 2019
Ensure documentation coverage and clean up of the various APIs. Fixes #1891 BREAKING CHANGE: * **core:** `StackProps.autoDeploy` has been removed and replaced by `StackProps.hide` (with negated logic). * **core:** `ISynthesizable.synthesize` now accepts an `ISynthesisSession` which contains the `CloudAssemblyBuilder` object. * **cx-api:** Multiple changes to the cloud assembly APIs to reduce surface area and clean up.
6 tasks
eladb
pushed a commit
that referenced
this issue
Jun 5, 2019
Fixes #1891 Testing: all toolkit integration tests passed. BREAKING CHANGE: * **cli:** This release requires CDK CLI >= 0.34.0 * **core:** `App.run()` was renamed to `App.synth()` (soft deprecation, it will be removed in the next release). * **core:** The `Stack.autoDeploy` feature has been removed. You can use `cdk deploy STACK ...` to determine which stacks to deploy (and wildcards are supported, so `cdk deploy '*'` will deploy all stacks. We plan to change the CLI to require specifying stacks if there is more than a single stack in the app (#2750). * **core:** `ConstructNode.aspects` is now private. * **core:** The `Synthesizer` has been removed. Use `ConstructNode.synth(node)` instead. * **core:** `ISynthesizable.synthesize` now accepts an `ISynthesisSession` which contains the `CloudAssemblyBuilder` object. This will allow further extension in the future. * **cx-api:** `cxapi.MissingContext` now includes the context `key` * **core:** `Stack.reportMissingContext` now accepts a single argument of type `cxapi.MissingContext`, which includes the missing context key * **core:** `Stack.annotatePhysicalName` has been removed (not used). * **core:** `Stack.missingContext` is now private. * **cx-api:** Multiple changes to the cloud assembly APIs to reduce surface area and clean up. * **cdk-integ (private):** if an integration test includes multiple stacks, use `/// !cdk-integ STACK ...` to explicitly specify which stacks to include in the test.
This was referenced Aug 22, 2019
This was referenced Dec 12, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Most of the
synthesizeStackandsynthesizeStacksare there mostly for testing purposes and legacy. We should probably revisit.Remove legacy and clean up so we don't have to break in the future.
The text was updated successfully, but these errors were encountered: