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

Adjust login and querying for regional data sovereignty changes #294

Open
clcollins opened this issue Jun 19, 2024 · 2 comments
Open

Adjust login and querying for regional data sovereignty changes #294

clcollins opened this issue Jun 19, 2024 · 2 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@clcollins
Copy link
Member

When OCM's split of cluster data into regional OCM endpoints has been completed upstream, we will need to adjust the ocm-container login automation to:

  • Query AMS for the subscription to which the cluster ID belongs
  • Get the regional OCM endpoint URL from the subscription
    • If none, use the global URL
  • Re-query the endpoint URL for the rest of the cluster information to perform login

As part of this issue, we need to also identify any other places data queried from OCM occurs in ocm-container and adjust these as well.

Done Criteria:

  • OCM Query code is centralized into a single generic package or function, which properly handles the regional OCM endpoints
  • OCM Container's login function is updated to use the new code
  • Other instances of OCM querying in ocm-container are identified and updated to use the new code
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 18, 2024
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

2 participants