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
{{ message }}
This repository has been archived by the owner on Dec 17, 2024. It is now read-only.
Since the account infrastructure base DA has an issue with cloud shell settings when using a service ID (or trusted profile), the default for skip_cloud_shell_calls should be set to true.
New or affected modules
By submitting this issue, you agree to follow our Code of Conduct
The text was updated successfully, but these errors were encountered:
@in-1911 I guess you wan't skip_cloud_shell_calls to default to true in the stack? But should we expose it as a stack level input incase someone is not using service ID or TP?
Technically we can expose it, but I think if we keep doing that, the stack inputs will become unmanageable.
The users still can change it at the DA level if there is a real need for that.
In this particular case, this option is not material for the solution functionality, and I do not remember that setting used in SCC profiles I used.
The drawback of setting the default in the stack is that the current projects functionality requires a manual user's input to override it while ignoring the matching values from the environment.
The problem with leaving it enabled is that the error is rather vague and it's not even documented in the Account Infra Base that you have to turn it off if using trusted profile or a service ID for deployment.
Description
Since the account infrastructure base DA has an issue with cloud shell settings when using a service ID (or trusted profile), the default for
skip_cloud_shell_calls
should be set totrue
.New or affected modules
By submitting this issue, you agree to follow our Code of Conduct
The text was updated successfully, but these errors were encountered: