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

T671: do not preserve old tech-support report implementation #2260

Merged
merged 1 commit into from Sep 13, 2023

Conversation

jestabro
Copy link
Contributor

Change Summary

This is needed after
vyos/vyatta-op#67
to expose the tech-support node and avoid empty node error.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes)
  • Migration from an old Vyatta component to vyos-1x, please link to related PR inside obsoleted component
  • Other (please describe):
    Remove old/dead code.

Related Task(s)

Component(s) name

Proposed changes

How to test

Checklist:

  • I have read the CONTRIBUTING document
  • I have linked this PR to one or more Phabricator Task(s)
  • I have run the components SMOKETESTS if applicable
  • My commit headlines contain a valid Task id
  • My change requires a change to the documentation
  • I have updated the documentation accordingly

@jestabro jestabro self-assigned this Sep 13, 2023
@vyosbot vyosbot requested review from a team, dmbaturin, sarthurdev, zdc, sever-sever and c-po and removed request for a team September 13, 2023 17:44
@c-po c-po merged commit 0a0aff8 into vyos:current Sep 13, 2023
8 checks passed
@c-po
Copy link
Member

c-po commented Sep 13, 2023

@Mergifyio backport sagitta

@mergify
Copy link

mergify bot commented Sep 13, 2023

backport sagitta

✅ Backports have been created

jestabro added a commit that referenced this pull request Sep 14, 2023
T671: do not preserve old tech-support report implementation (backport #2260)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 participants