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

Operations controller #554

Merged
merged 4 commits into from
Jan 23, 2025
Merged

Operations controller #554

merged 4 commits into from
Jan 23, 2025

Conversation

arbulu89
Copy link
Contributor

Description

Expose the operations through the http api.
I have chosen /api/v1/operations/executions for no particular reason. I didn't want to put simply /api/v1/operations, as maybe we want to add other things to operations. Anyway, this is guarded with a compilation environment, so we can change without any real consequence by now.

The operations_enable configuration entry is to avoid shipping this to prod before we have all the features in place

How was this tested?

UT

@arbulu89 arbulu89 added the enhancement New feature or request label Jan 22, 2025
@arbulu89 arbulu89 requested a review from CDimonaco January 22, 2025 08:45
@coveralls
Copy link
Collaborator

coveralls commented Jan 22, 2025

Coverage Status

coverage: 97.422% (+0.08%) from 97.338%
when pulling f9eb417 on operations-controller
into 8f9219d on main.

@arbulu89 arbulu89 marked this pull request as ready for review January 22, 2025 10:11
@arbulu89 arbulu89 merged commit e410c59 into main Jan 23, 2025
13 checks passed
@arbulu89 arbulu89 deleted the operations-controller branch January 23, 2025 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

Successfully merging this pull request may close these issues.

3 participants