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

[3006.x] Make sure the file client is destroyed upon used #64113

Merged
merged 5 commits into from
Apr 28, 2023

Commits on Apr 26, 2023

  1. Make sure the file client is destroyed upon used

    Signed-off-by: Pedro Algarvio <[email protected]>
    s0undt3ch committed Apr 26, 2023
    Configuration menu
    Copy the full SHA
    033ab0d View commit details
    Browse the repository at this point in the history
  2. Don't cache the file client

    Signed-off-by: Pedro Algarvio <[email protected]>
    s0undt3ch committed Apr 26, 2023
    Configuration menu
    Copy the full SHA
    109c456 View commit details
    Browse the repository at this point in the history
  3. Add regression test for saltstack#64111

    Test importing jinja files
    dwoz authored and s0undt3ch committed Apr 26, 2023
    Configuration menu
    Copy the full SHA
    11968b8 View commit details
    Browse the repository at this point in the history
  4. Don't cache the file client at the class level

    Signed-off-by: Pedro Algarvio <[email protected]>
    s0undt3ch committed Apr 26, 2023
    Configuration menu
    Copy the full SHA
    72c5a87 View commit details
    Browse the repository at this point in the history
  5. Add unit test to validate logic on calls to destroy()

    Signed-off-by: Pedro Algarvio <[email protected]>
    s0undt3ch committed Apr 26, 2023
    Configuration menu
    Copy the full SHA
    b14cf05 View commit details
    Browse the repository at this point in the history