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

Optimize Data Import can still be run after becoming part of Single Application #24828

Open
9 tasks
Tracked by #794
RomanJRW opened this issue Nov 18, 2024 · 0 comments
Open
9 tasks
Tracked by #794
Labels
component/optimize Related to Optimize component/team kind/task Categorizes an issue as a breakdown of low-level implementation detail from a parent issue

Comments

@RomanJRW
Copy link
Contributor

Context

After moving to the Single Application, Optimize must still be able to import data to its data indices. Other parts of the single application will no longer do this, but Optimize will continue to do so for the time being.

Acceptance Criteria

  • In SaaS, Optimize can still import data to be used by all Optimize instances
  • In C8SM (Helm Charts), Optimize can still import data to be used by all Optimize instances

Testing Notes

Links

Breakdown

Pull Requests

No tasks being tracked yet.

Task Lifecycle

For managing the issue lifecycle, please use the workflow commands. You can see the available
commands by writing /help as a comment on this issue.

Review

Engineering Review

  • All code targeting the main branch has been reviewed by at least one Engineer
  • The PR targeting the main branch has been approved by the reviewing Engineer
  • If the API has changed, the API documentation is updated
  • All other PRs (docs, controller etc.) in the breakdown have been approved

QA Review

  • The change is implemented as described on all target environments/versions/modes
  • The documentation changes are as expected

Completion

  • All Review stages are successfully completed
  • All associated PRs are merged to the main branch(es) and stable branches
  • The correct version labels are applied to the issue
@RomanJRW RomanJRW added kind/task Categorizes an issue as a breakdown of low-level implementation detail from a parent issue component/optimize Related to Optimize component/team labels Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/optimize Related to Optimize component/team kind/task Categorizes an issue as a breakdown of low-level implementation detail from a parent issue
Projects
None yet
Development

No branches or pull requests

1 participant