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 means that the direct argument takes precedence over the AWS_PROFILE env var. However, at the same time, it's not possible to define this locally, and override it for CI...that is to say use a different profile in each environment.
Expected Behavior
There should be a mechanism to allow us to specify a different profile in each env, or at least to not interfere with the native AWS env vars. For instance, removing the profile field from my nx.json allows caching to work in CI because it uses our AWS_PROFILE (but this isn't defined locally by default).
GitHub Repo
No response
Steps to Reproduce
Install s3-client
Configure nxJson with any ssoProfile value
Notice that AWS_PROFILE is not used in the credentials
Current Behavior
Right now, the plugin appears to instantiate the aws profile from the
nxJson.ssoProfile
:This means that the direct argument takes precedence over the AWS_PROFILE env var. However, at the same time, it's not possible to define this locally, and override it for CI...that is to say use a different profile in each environment.
Expected Behavior
There should be a mechanism to allow us to specify a different profile in each env, or at least to not interfere with the native AWS env vars. For instance, removing the profile field from my nx.json allows caching to work in CI because it uses our AWS_PROFILE (but this isn't defined locally by default).
GitHub Repo
No response
Steps to Reproduce
ssoProfile
valueAWS_PROFILE
is not used in the credentialsNx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
Notice that the community plugins dodge this problem by preferring env vars:
https://github.com/robinpellegrims/pellegrims/blob/e5269065f0676a4e47731219ba85dbd5a2d18cf9/libs/nx-remotecache-s3/src/lib/s3-client.ts#L81
It'd be reasonable to just look for AWS_PROFILE and use that first if it exists...or to create a new NX_AWS_PROFILE.
The text was updated successfully, but these errors were encountered: