Skip to content

feat(#268): New Kit: Cisco ASA & Cisco FTD - Initial Release#269

Open
kyle-mallett-gravwell wants to merge 9 commits into
gravwell:mainfrom
kyle-mallett-gravwell:cisco
Open

feat(#268): New Kit: Cisco ASA & Cisco FTD - Initial Release#269
kyle-mallett-gravwell wants to merge 9 commits into
gravwell:mainfrom
kyle-mallett-gravwell:cisco

Conversation

@kyle-mallett-gravwell
Copy link
Copy Markdown
Contributor

Cisco ASA & Cisco FTD Kit(s)

What is the feature to be added?

  • Make a kit for Cisco ASA
  • Make a kit for Cisco FTD

Why should we add this feature? (Business justification? What problem is the feature trying to solve?)

Useful for customers utilizing that product.

How does this feature address the above problem?

Makes getting up and running faster for Cisco ASA/FTD logs

Any other comments?

#268

This PR addresses [ISSUE_LINK]

This PR proposes...

PR Tasks

  • e2e and/or unit tests included. If not, please provide an explanation.
  • Bug fixes only: minimal repro steps included on the issue (for PR QA + Release QA).

Reviewer Tasks

  • e2e or unit tests are present to test the proposed changes.
  • Code is sufficiently documented.
  • Code meets quality and correctness expectations.

This PR addresses [ISSUE_LINK]

This PR proposes...

PR Tasks

  • e2e and/or unit tests included. If not, please provide an explanation.
  • Bug fixes only: minimal repro steps included on the issue (for PR QA + Release QA).

Reviewer Tasks

  • e2e or unit tests are present to test the proposed changes.
  • Code is sufficiently documented.
  • Code meets quality and correctness expectations.

This PR addresses [ISSUE_LINK]

This PR proposes...

PR Tasks

  • e2e and/or unit tests included. If not, please provide an explanation.
  • Bug fixes only: minimal repro steps included on the issue (for PR QA + Release QA).

Reviewer Tasks

  • e2e or unit tests are present to test the proposed changes.
  • Code is sufficiently documented.
  • Code meets quality and correctness expectations.

# Cisco ASA & Cisco FTD Kit(s)

## What is the feature to be added?
- Make a kit for Cisco ASA
- Make a kit for Cisco FTD

## Why should we add this feature? (Business justification? What problem is the feature trying to solve?)

Useful for customers utilizing that product.

## How does this feature address the above problem?

Makes getting up and running faster for Cisco ASA/FTD logs

## Any other comments?

gravwell#268

<!--

The title of this PR should have the form:  [TYPE]([ISSUE_NUMBER]): [CHANGELOG_MESSAGE]

- If [TYPE] is fix or feat, the CHANGELOG_MESSAGE will be included in customer-facing, release change logs.
- Other [TYPE]s WILL NOT be included in release change logs.
- Check out https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#type for other type ideas, or invent your own.

-->

This PR addresses [[ISSUE_LINK](gravwell#268)]

## This PR proposes...

-

## PR Tasks

<!-- Add tasks to this list as needed -->

- [ ] e2e and/or unit tests included. If not, please provide an explanation.
- [ ] **Bug fixes only:** minimal repro steps included on the issue (for PR QA + Release QA).

## Reviewer Tasks

<!-- Add tasks to this list as needed -->

- [ ] e2e or unit tests are present to test the proposed changes.
- [ ] Code is sufficiently documented.
- [ ] Code meets quality and correctness expectations.

<!--

The title of this PR should have the form:  [TYPE]([ISSUE_NUMBER]): [CHANGELOG_MESSAGE]

- If [TYPE] is fix or feat, the CHANGELOG_MESSAGE will be included in customer-facing, release change logs.
- Other [TYPE]s WILL NOT be included in release change logs.
- Check out https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#type for other type ideas, or invent your own.

-->

This PR addresses [ISSUE_LINK]

## This PR proposes...

-

## PR Tasks

<!-- Add tasks to this list as needed -->

- [ ] e2e and/or unit tests included. If not, please provide an explanation.
- [ ] **Bug fixes only:** minimal repro steps included on the issue (for PR QA + Release QA).

## Reviewer Tasks

<!-- Add tasks to this list as needed -->

- [ ] e2e or unit tests are present to test the proposed changes.
- [ ] Code is sufficiently documented.
- [ ] Code meets quality and correctness expectations.
@kyle-mallett-gravwell kyle-mallett-gravwell self-assigned this Mar 18, 2026
@kyle-mallett-gravwell
Copy link
Copy Markdown
Contributor Author

@mike-wade-gravwell when you get the chance

@kris-watts-gravwell
Copy link
Copy Markdown
Contributor

assigning bronson for review

@kris-watts-gravwell kris-watts-gravwell removed the request for review from mike-wade-gravwell April 16, 2026 00:44
@bronson-peto-gravwell
Copy link
Copy Markdown
Collaborator

Holding off on approving these while we check into any broader changes we may look to make with kits in Q2 release. Would like to include any additional adjustments if we already are going to be updating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants