APP-4896: Implement GetAuthApplication API

[jr22]

APP-4896

Implementing GetAuthApplication API that will eventually result in CLI command with format:

viam auth-app get --org-id=c6215428-1b73-41c3-b44a-56db0631c8f1 --application-id=6847e7a9-d7bd-4603-9655-bdc24370342a 
{
	"application_id": "6847e7a9-d7bd-4603-9655-bdc24370342a",
	"application_name": "julias app",
	"secret": "supersupersecretsecret"
	"origin_uris": ["https://test.com", "https://test2.com" ],
	"redirect_uris": ["https://redirect.com", "https://redirect2.com" ],
	"logout_uri": "https://logout.com",
}

[ohEmily]

[minor] maybe we rename to client_secret to match FusionAuth's application.oauthConfiguration.clientSecret from their API? also makes it a little easier to grep for this string.

[jr22]

yeah makes sense to me. i can also rename the secret field in the RegisterAuthApplication request here to client_secret then?

[ohEmily]

Thank you! Added a small comment.

[jr22]

workflow is broken for api changes -> fixing here

[ohEmily]

Weird that changing this broke the linter suite. Seems like a linter bug. To unblock your PR you could squash the changes.

/ Test For Lint and Breaking Changes
Field "3" with name "client_secret" on message "RegisterAuthApplicationResponse" changed option "json_name" from "secret" to "clientSecret".
 Check failure on line 47 in proto/viam/app/v1/end_user.proto

/ Test For Lint and Breaking Changes
Field "3" on message "RegisterAuthApplicationResponse" changed name from "secret" to "client_secret".

[jr22]

Weird that changing this broke the linter suite. Seems like a linter bug. To unblock your PR you could squash the changes.

/ Test For Lint and Breaking Changes
Field "3" with name "client_secret" on message "RegisterAuthApplicationResponse" changed option "json_name" from "secret" to "clientSecret".
 Check failure on line 47 in proto/viam/app/v1/end_user.proto

/ Test For Lint and Breaking Changes
Field "3" on message "RegisterAuthApplicationResponse" changed name from "secret" to "client_secret".

Its a breaking change for me to change the RegisterAuthResponse field from secret -> client_secret so i think this failure is expected?

[ohEmily]

Weird that changing this broke the linter suite. Seems like a linter bug. To unblock your PR you could squash the changes.

/ Test For Lint and Breaking Changes
Field "3" with name "client_secret" on message "RegisterAuthApplicationResponse" changed option "json_name" from "secret" to "clientSecret".
 Check failure on line 47 in proto/viam/app/v1/end_user.proto

/ Test For Lint and Breaking Changes
Field "3" on message "RegisterAuthApplicationResponse" changed name from "secret" to "client_secret".

Its a breaking change for me to change the RegisterAuthResponse field from secret -> client_secret so i think this failure is expected?

Oh what I meant is that it seems dumb to consider it a "breaking" change when it's comparing to an earlier version of the same PR. IMO it should only compare to main, not to the current branch.

[jr22]

Weird that changing this broke the linter suite. Seems like a linter bug. To unblock your PR you could squash the changes.

/ Test For Lint and Breaking Changes
Field "3" with name "client_secret" on message "RegisterAuthApplicationResponse" changed option "json_name" from "secret" to "clientSecret".
 Check failure on line 47 in proto/viam/app/v1/end_user.proto

/ Test For Lint and Breaking Changes
Field "3" on message "RegisterAuthApplicationResponse" changed name from "secret" to "client_secret".

Its a breaking change for me to change the RegisterAuthResponse field from secret -> client_secret so i think this failure is expected?

Oh what I meant is that it seems dumb to consider it a "breaking" change when it's comparing to an earlier version of the same PR. IMO it should only compare to main, not to the current branch.

It is comparing to main though. On main the "RegisterAuthApplicationResponse" has "secret" not "client_secret". Maybe im not understanding your q?