You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A year and a half ago, I filed an issue about missing properties from the Google\Service\Iam class related to service accounts. The somewhat unsatisfactory response was "v2 is now the dominant version, so support for v1 was dropped." This effectively prohibits anyone from updating to a version of 0.286.0 or newer, if they use the library to create service accounts.
Describe the solution you'd like
I would like to have support for both v1 and v2 of the IAM API. As we are nowhere close to feature parity, I am lead to believe this is not Google's intent and both versions have different purposes. This is further strengthened by the fact that both the Java client and the Go client have support for both versions:
Describe alternatives you've considered
A suggestion in the previous issue was using low level calls to interact with the API. This is not a viable option as we prefer readable and maintainable code for our projects.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A year and a half ago, I filed an issue about missing properties from the
Google\Service\Iam
class related to service accounts. The somewhat unsatisfactory response was "v2 is now the dominant version, so support for v1 was dropped." This effectively prohibits anyone from updating to a version of 0.286.0 or newer, if they use the library to create service accounts.Describe the solution you'd like
I would like to have support for both v1 and v2 of the IAM API. As we are nowhere close to feature parity, I am lead to believe this is not Google's intent and both versions have different purposes. This is further strengthened by the fact that both the Java client and the Go client have support for both versions:
Describe alternatives you've considered
A suggestion in the previous issue was using low level calls to interact with the API. This is not a viable option as we prefer readable and maintainable code for our projects.
The text was updated successfully, but these errors were encountered: