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
I'm running in a small locked-down environment with very few variables set; in particular, I'm running without an existent HOME directory. I've configured the client to use non-default providers for credentials and region. However, when initializing, the client still emits half a dozen warning messages via tracing about not finding a home directory, from src/profile/parser/source.rs within aws-config. I'm not running on Lambda, but I'm in the same category where this warning isn't helpful.
I'd like to be able to easily disable all attempts to access HOME. (Ideally, I don't just want to suppress the warning; I'd like to suppress the actual attempts, and associated initialization time.)
Expected Behavior
Some means of suppressing the attempts to access HOME.
Current Behavior
Half a dozen warnings through tracing saying could not determine home directory but home expansion was requested, from src/profile/parser/source.rs within aws-config.
[package]
name = "foo"version = "0.1.0"edition = "2021"
[dependencies]
anyhow = "1.0.58"async-std = { version = "1.12.0", features = ["attributes", "tokio1"] }
aws-config = { version = "0.15.0", default-features = false, features = ["rustls"] } # rustls feature required to work around compilation erroraws-sdk-sts = { version = "0.15.0", default-features = false }
aws-smithy-client = "0.45.0"http = "0.2.8"hyper-rustls = { version = "0.23.0", default-features = false, features = ["http1", "http2", "tls12", "webpki-roots", "webpki-tokio"] }
tracing = { version = "0.1.29", features = ["max_level_info", "release_max_level_info"] }
tracing-subscriber = { version = "0.3.11", default-features = false, features = ["fmt"] }
Possible Solution
No response
Additional Information/Context
For reproducing this, it may help to build with --target x86_64-unknown-linux-musl, and put the resulting binary into a chroot, with just an /etc/resolv.conf and nothing else. Run it with chroot and an unset HOME.
After digging into this a bit, I realized our original assessment on next steps wouldn't improve the situation. I took a different approach of only emitting the warning if the profile path was explicitly overridden in smithy-lang/smithy-rs#1558.
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
I'm running in a small locked-down environment with very few variables set; in particular, I'm running without an existent HOME directory. I've configured the client to use non-default providers for credentials and region. However, when initializing, the client still emits half a dozen warning messages via
tracing
about not finding a home directory, fromsrc/profile/parser/source.rs
withinaws-config
. I'm not running on Lambda, but I'm in the same category where this warning isn't helpful.I'd like to be able to easily disable all attempts to access HOME. (Ideally, I don't just want to suppress the warning; I'd like to suppress the actual attempts, and associated initialization time.)
Expected Behavior
Some means of suppressing the attempts to access HOME.
Current Behavior
Half a dozen warnings through
tracing
sayingcould not determine home directory but home expansion was requested
, fromsrc/profile/parser/source.rs
withinaws-config
.Reproduction Steps
src/main.rs
:Cargo.toml
:Possible Solution
No response
Additional Information/Context
For reproducing this, it may help to build with
--target x86_64-unknown-linux-musl
, and put the resulting binary into a chroot, with just an/etc/resolv.conf
and nothing else. Run it with chroot and an unset HOME.Version
Environment details (OS name and version, etc.)
Debian, latest sid
Logs
No response
The text was updated successfully, but these errors were encountered: