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.

Sign up for GitHub

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

Jump to bottom

"Config" only deployment fails validation when Existing CloudTrail Name is empty #7

Open
jvogt opened this issue Nov 1, 2023 · 0 comments
Open

"Config" only deployment fails validation when Existing CloudTrail Name is empty #7

jvogt opened this issue Nov 1, 2023 · 0 comments

Comments

@jvogt
Copy link

jvogt commented Nov 1, 2023 •
edited
Loading

When deploying in Config-only mode, the Existing CloudTrail parameter would logically be left empty. But the constraint on the ExistingCloudTrail parameter has a minimum length of 1.

I suggest either making the ExistingCloudTrail parameter optional, or adding a hint to the ExistingCloudTrail description to use the value of "none" in order to satisfy the constraints.

I was going to open a PR but do not have permissions to do so.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jvogt