chore: use CDK v1 API for lacework component dev #1525
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jon-stewart
approved these changes
Jan 29, 2024
PengyuanZhao
force-pushed
the
pengyuan/GROW-2597
branch
from
bacfd63
to
9f8838a
Compare
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
For the
lacework component devcommand:.devspecs file exists, show the version value in.devinstead of.version(same behavior as prototype code).How did you test this change?
lacework component dev test-componentto test a new component is created correctly in dev modelacework component install spm-opaandlacework component dev spm-opato test an installed component is moved into dev mode.Issue
https://lacework.atlassian.net/browse/GROW-2597