Skip to content

feat: report workspaceId, backend and loginType in the organization workspace report - #116

Open
jirkasemmler wants to merge 1 commit into
mainfrom
jirka/describe-workspaces-login-type
Open

feat: report workspaceId, backend and loginType in the organization workspace report#116
jirkasemmler wants to merge 1 commit into
mainfrom
jirka/describe-workspaces-login-type

Conversation

@jirkasemmler

Copy link
Copy Markdown
Contributor

Changes:

  • manage:describe-organization-workspaces now reports loginType (snowflake-legacy-service = password, *-keypair / *-sso = already migrated), so an organization can be audited for the Snowflake password-authentication deprecation without joining the report against a separate export of Snowflake users.
  • Added workspaceId - it is the input manage:delete-project-workspaces-by-id takes, so a row of this report now feeds straight into the deletion step instead of needing a second lookup - and backend.
  • Fixed a typo that made the command unusable: lismkdirtWorkspaces() is not a method on the Workspaces client, so every invocation died with a fatal error.
  • README: updated the CSV header and documented the new columns.

The new columns are appended in place rather than at the end of the row, so anything parsing this CSV by column name keeps working; anything parsing it by position does not.


Additional notes

⚠️ Don't forget to release new version after merge

Same as #115: the 4 phpstan errors in FlowMigration/ProjectClientsFactory.php are pre-existing on main at c4ef6b4 and unchanged by this PR. Locally phpunit (76 tests) and phpcs are green.

🤖 Generated with Claude Code

…eport

`manage:describe-organization-workspaces` described what each workspace is for
but not how its backend user authenticates, so auditing an organization ahead of
the Snowflake password-authentication deprecation meant joining the report
against a separate export of Snowflake users just to tell password workspaces
from key-pair ones. `loginType` answers that directly.

`workspaceId` is added for the same reason: it is what
`manage:delete-project-workspaces-by-id` takes as input, so a row of this report
can now be fed straight into the deletion step instead of being looked up again.
`backend` comes along because it is free and the report already spans backends.

Also fixes a typo that made the command unusable: `lismkdirtWorkspaces()` is not
a method on the Workspaces client, so every invocation died with a fatal error.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant