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.

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

Add option to compare between local and deployed configurations #844

Open
1 task done
eladbs opened this issue Aug 17, 2023 · 2 comments
Open
1 task done

Add option to compare between local and deployed configurations #844

eladbs opened this issue Aug 17, 2023 · 2 comments

Comments

@eladbs
Copy link

eladbs commented Aug 17, 2023

Checklist

Describe the problem you'd like to have solved

Hi,
Today our CI/CD workflow with the deploy CLI tool is lacking the option to compare between the local and the deployed configuration.
We use gitops for publishing configuration to our tenants. Each new PR is reviewed against the deployed configuration and approved before being merged.
We want the ability to compare each of the files against the deployed version.
Need to support yaml, js and html.

Describe the ideal solution

Add the option to compare. For i.e., to run:

a0deploy compare --config_file=config.json --input-folder=~/local

This should result in a proper diff view of the changes between the configuration in the ~/local folder and the configuration deployed in the tenant.

Alternatives and current workarounds

There are 3rd party diff/compare tools but they lack support for the custom attribute mapping in the config and they are not context aware, just comparing text line by line.

Additional context

No response

@willvedd
Copy link
Contributor

@eladbs Solid idea but do you think this is different than #70?

@eladbs
Copy link
Author

eladbs commented Aug 24, 2023

As I see it, #70 is more about to check if a configuration is valid, schema wise. I.e., can it be deployed with no errors.
Going over those large files to look if a change has been implemented correctly, and without affecting other configs, is hard.
This is especially true with mappings and exclusions (that behave differently in import/export b.t.w.).
For our CI/CD flow #70 is less important but I can see how it can help others.

If I may give an example of such tool, Kong Deck is one: https://docs.konghq.com/deck.
It supports both feature requests and more.

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

No branches or pull requests

2 participants