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
This seems like a misplaced validation. The StarLarky repo should not care about the names of VGS alias formats. It should just have an interface that handles exceptions in case the runtime determines that the alias format is not supported.
Having to update StarLarky every time a new Alias format is created does not seem like an appropriate workflow.
The text was updated successfully, but these errors were encountered:
Are you planning on exposing to customers the alias formats via Larky? If so, can it be an enum that you can override by passing in a string until larky is updated?
The ask is to remove the list of alias formats from Larky completely. I do not want to update VaultModule.java in the StarLarky repo when we release new alias formats.
Larky will get a response from the Vault (or some other service that is responsible for responding to the vault module) if the alias format was not appropriate.
ea0adcf#diff-cf5faff91ae9cd74b7b9d2504673969166da7d94e0b519c53f7b0dfaa2fd856f
This seems like a misplaced validation. The StarLarky repo should not care about the names of VGS alias formats. It should just have an interface that handles exceptions in case the runtime determines that the alias format is not supported.
Having to update StarLarky every time a new Alias format is created does not seem like an appropriate workflow.
The text was updated successfully, but these errors were encountered: