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 updated lsst-sqre/build-and-push-to-ghcr to the latest tagged version. This got the container to build, but it still couldn't load snapshots.
Remove the profile specification from the localized snapshot URIs, because the way the container app is set up it needs to be the default. But, running on a USDF devel node still needs to be set to use the lfa profile. The profile the dashboard uses can still be set with the AWS_PROFILE environment variable, so if it fails and it looks like this was the issue, there's a longer error message suggesting setting it.
Remove the profile specification from the localized snapshot URIs, because the way the container app is set up it needs to be the default.
is because the secret being injected from vault is the "default" AWS credentials, and not the "lfa" credentials (but default works ok for reading)?
I'm less clear on why the default doesn't work from the dev nodes.
Remove the profile specification from the localized snapshot URIs, because the way the container app is set up it needs to be the default.
is because the secret being injected from vault is the "default" AWS credentials, and not the "lfa" credentials (but default works ok for reading)? I'm less clear on why the default doesn't work from the dev nodes.
Yes, it needs to use the default profile in the credential file provided to the phalanx container. This is not the same as the default profile on the USDF devel nodes, but a special purpose credential file created just for this app. See the discussion in the relevant pull request.
I'm pretty sure the default profile in the USDF devel nodes also used to work, but it seems not to work anymore: we need to use the lfa profile in the devel nodes instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two changes were required: