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

chore: Disable legacy upload #4160

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

m-horky
Copy link
Contributor

@m-horky m-horky commented Jul 10, 2024

All Pull Requests:

Check all that apply:

  • Have you followed the guidelines in our Contributing document, including the instructions about commit messages?
  • Is this PR to correct an issue?
  • Is this PR an enhancement?

Complete Description of Additions/Changes:

  • Card ID: CCT-252
  • Card ID: RHENING-7569

This patch disables the legacy APIs. The code and configuration option will be removed later; this is the first step to get rid of the duplication and differences.

Only the absolutely necessary changes were made to tests; without these removals the suite wouldn't pass.

@m-horky m-horky force-pushed the rhening-7569/disable-legacy branch 3 times, most recently from 45accfd to 759ef5f Compare July 10, 2024 11:06
@xiangce
Copy link
Contributor

xiangce commented Jul 17, 2024

Sorry for the abrupt comment before this PR being ready😅, but from the description of RHINENG-7569, the task is also trying to replace the API for legacy_upload=False from cert-api.access.redhat.com/r/insights to cert.console.redhat.com/api. If this is already in your next plan, please ignore this.

BTW, it seems that the CCT-252 is more suitable to be linked to this PR.

@m-horky
Copy link
Contributor Author

m-horky commented Jul 17, 2024

It's fine.

  • You are right, CCT-252 is a better tracking ticket, I must have missed it.
  • The API URL will be handled via CCT-258 in a separate PR, we don't want to make too many changes at once to prevent regressions.

@m-horky m-horky force-pushed the rhening-7569/disable-legacy branch from 759ef5f to c3a20a2 Compare July 17, 2024 09:31
@xiangce xiangce added the client These issues represent work to be done by the "client" team. label Aug 26, 2024
@xiangce
Copy link
Contributor

xiangce commented Sep 5, 2024

Hi @m-horky - - Sorry for bringing this trouble to you, as we just resolved an urgent bug within the repo. Please rebase the master branch of your fork of insights-core and then rebase this branch again. Please reach out to me for any problems when doing the rebase. Apologize again.

@m-horky m-horky force-pushed the rhening-7569/disable-legacy branch from c3a20a2 to d30e6d7 Compare September 5, 2024 13:25
* Card ID: CCT-252
* Card ID: RHINENG-7569

This patch disables the legacy APIs. The code and configuration option
will be removed later; this is the first step to get rid of the
duplication and differences.

Only the absolutely necessary changes were made to tests; without these
removals the suite wouldn't pass. The rest will be cleaned up later.

Signed-off-by: mhorky <[email protected]>
@m-horky m-horky force-pushed the rhening-7569/disable-legacy branch from d30e6d7 to b1f9ca4 Compare September 12, 2024 11:51
@jenkins-qa-bot
Copy link
Collaborator

Can one of the admins verify this patch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client These issues represent work to be done by the "client" team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants