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.

Sign up for GitHub

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

Jump to bottom

docs(changelog): add info about allowed operations in orca #237

Merged
merged 1 commit into from
Sep 6, 2022
Merged

docs(changelog): add info about allowed operations in orca #237

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
16 changes: 15 additions & 1 deletion content/en/docs/releases/next-release-preview/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,11 +90,25 @@ Addition of instance type metadata/ information to API response. See before-afte


### Orca
- Changes to adapt Igor API changes:
- Changes to adapt to Igor API changes:
- Introduce a feature flag in Orca to use the new Igor `stop` endpoint. By default, if not enabled the existing endpoint (`PUT /masters/{name}/jobs/{jobName}/stop/{queuedBuild}/{buildNumber}`) will be called
```
feature:
igor:
jobNameAsQueryParameter: true
```
See the changes [here](https://github.com/spinnaker/orca/pull/4294)

- https://github.com/spinnaker/orca/pull/4195 provides a way to limit the operations that orca performs, either globally, or for specific users. For example:

```
executions:
blockOrchestrationExecutions: true
allowedOrchestrationExecutions: # only applicable when blockOrchestrationExecutions: false
- name: updateApplication # eg. config to show how to set the name and allowAllUsers properties for an execution
allowAllUsers: true
- name: saveApplication # eg. config to show how to set just the name of an execution. It defaults to allowAllUsers: true
- name: savePipeline # eg. config to show how to set the name and permittedUsers properties for an execution
permittedUsers:
- "permitted-user@abc.com"
```