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

Accept output from one Katana run to parse as a diff against another run #146

Open
neilwillgettoit opened this issue Nov 8, 2022 · 1 comment
Open

Accept output from one Katana run to parse as a diff against another run #146

neilwillgettoit opened this issue Nov 8, 2022 · 1 comment
Labels
Priority: Low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@neilwillgettoit
Copy link

I would like to have the output of one katana run be able to be fed into another katana run and produce a diff from the first run.

The workflow would be: 1. Run katana against site, save output 2. Pass output as a difference flag to another katana instance and produce only the differences between the first run and the second run.

Why would I like this? It would make it much easier to parse A/B testing on sites from various source IPs. I could do one run from us-east and then a second run from us-west to see what/if is different between the two runs from the two locations. On the second run from us-west I’d like to see just the diff from us-east output.
@neilwillgettoit neilwillgettoit added the Type: Enhancement Most issues will probably ask for additions or changes. label Nov 8, 2022
@neilwillgettoit neilwillgettoit changed the title Accept output from one Katana run to as a diff against another run Accept output from one Katana run to parse as a diff against another run Nov 8, 2022
@Mzack9999
Copy link
Member

Might be a follow up of #13

@ehsandeep ehsandeep added the Priority: Low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix label Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: Low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ehsandeep @Mzack9999 @neilwillgettoit