Skip to content

v1.14.2

Choose a tag to compare

View all tags
@thde thde released this 26 Feb 10:03
· 19 commits to main since this release
v1.14.2
fb83747

Changelog

If you're using nctl auth set-project in CI with an APIServiceAccount you'll need to update the command to run nctl auth set-project --force.

Details

Until v1.14.0 nctl auth set-project would set a project without verifying if the user has access to that project in the first place. This led to confusion for users and therefore we introduced an error and suggestions how to verify which projects a user belongs to.

In some cases, nctl is unable to verify if it has access to a project and would always throw an error:

  1. When using an APIServiceAccount in a sub-project.
  2. When using an APIServiceAccount without organizational access.

The nctl auth set-project --force flag allows you to override these checks and set a project anyway.

What's Changed

  • fix: allow to force setting a project even if it can't be listed by @thde in #357

Full Changelog: v1.14.1...v1.14.2

Contributors

thde
Assets 13
Loading