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

bug: ReadCurrentWithOptions semantics changed #601

Closed
fsaintjacques opened this issue Sep 13, 2023 · 0 comments · Fixed by #603
Closed

bug: ReadCurrentWithOptions semantics changed #601

fsaintjacques opened this issue Sep 13, 2023 · 0 comments · Fixed by #603

Comments

@fsaintjacques
Copy link
Contributor

Reading the latest outputs of a workspace seems to fail, from the client we see the following error

client.StateVersions.ReadCurrentWithOptions: Internal Server Error

retrieving included resource: access to the resource is not permitted

From the service:

jsonPayload: {
action: 80
error: null
level: "ERROR"
msg: "unauthorized action"
organization: "..."
subject: {6}
workspace_id: "..."
}
@leg100 leg100 mentioned this issue Sep 13, 2023
Merged
leg100 added a commit that referenced this issue Sep 13, 2023
@leg100
fix: retrieving state outputs only requires read role (#603)
25c4a99 
Fixes #601.

Retrieving the current state outputs should not require organization
ownership, only a read role on the workspace or a workspace admin role.
This PR addresses that.

Also refactors the output retrieval code: instead of retrieving each
output one by one, all outputs are retrieved at once.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: retrieving state outputs only requires read role leg100/otf
1 participant
@fsaintjacques