diff --git a/README.md b/README.md
index 2b408ec..3235c9e 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
| AppVeyor | Travis | Azure Pipelines |
| --- | --- | --- |
-| [](https://ci.appveyor.com/project/emgarten/sleet) | [](https://travis-ci.com/emgarten/Sleet) | [](https://github.com/emgarten/sleet) |
+| [](https://ci.appveyor.com/project/emgarten/sleet) | [](https://github.com/emgarten/sleet) |
# What is Sleet?
@@ -11,9 +11,15 @@ Sleet is a static NuGet package feed generator.
* **Serverless**. Create static feeds directly on *Azure Storage*, *Amazon S3* or another S3 compatible storage. No compute required.
* **Cross platform**. Sleet is built in .NET, it can run on *.NET Framework*, *Mono*, or [dotnet CLI](https://github.com/dotnet/cli)
* **Fast.** Static feeds are created using the [NuGet v3 feed format](https://docs.microsoft.com/en-us/nuget/api/overview).
-* **Symbol server.** Assemblies and pdb files from packages are automatically indexed and provided as a [symbol server](doc/symbol-server.md).
* **Simple.** Sleet is a simple command line tool that can add, remove, and update packages.
-* **Flexible.** Feeds can be written to disk and hosted with a web server to support authentication. Use the command line tool or a library to run Sleet programmatically.
+* **Flexible.** Configuration and credentials can be set using files, env vars, command line args, or AWS specific patterns to support a variety of workflows and CI builds.
+
+## Why use static feeds?
+
+* Package binaries are typically kept outside of git repos, static feeds provide a long term storage solution that can be paired with checked in code.
+* NuGet feeds are typically read for restore far more than they are updated.
+* Cloud storage accounts are a cheap and secure way to share nupkgs for public feeds.
+* You keep full control of your packages.
## Getting Sleet
@@ -48,13 +54,24 @@ CI builds are located on the following NuGet feed:
The list of packages on this feed is [here](https://nuget.blob.core.windows.net/packages/sleet.packageindex.json).
+## Contributing
+
+We welcome contributions. If you are interested in contributing to Sleet report an issue or open a pull request to propose a change.
+
## Sleet is..
Cold static packages from the cloud. ☁️ + 📦 = ❄️
+## History
+
+Sleet was created to achieve the original goals of the NuGet v3 feed format: Provide maximum availability and performance for NuGet restore by using only static files.
+
+The v3 feed format was designed to do all compute when pushing a new package since updates are infrequent compared to the number of times a package is read for restore. Static files also remove the need to run a specific server to host the feed, allowing a simple file service to handle it.
+
## Related projects
* [Sleet.Azure](https://github.com/kzu/Sleet.Azure) provides MSBuild props/targets for running Sleet.
+* [Sleet.Search](https://github.com/emgarten/Sleet.Search) provides a search service for Sleet feeds.
## License
diff --git a/ReleaseNotes.md b/ReleaseNotes.md
index bdee877..ed38e9c 100644
--- a/ReleaseNotes.md
+++ b/ReleaseNotes.md
@@ -3,6 +3,7 @@
## 5.1.0
* Added net7.0 support
* Update AWS SDK
+* Added AWS SSO profile support
## 5.0.6
* Updated NuGet.* packages to 6.2.1
diff --git a/build/config.props b/build/config.props
index 9d9a171..b0652b9 100644
--- a/build/config.props
+++ b/build/config.props
@@ -10,6 +10,8 @@
1.5.0
3.7.103.40
3.7.101.38
+ 3.7.100.103
+ $(AWSSDKSSOVersion)
1.0.6
diff --git a/doc/feed-type-s3.md b/doc/feed-type-s3.md
index a0176e6..d1a7d19 100644
--- a/doc/feed-type-s3.md
+++ b/doc/feed-type-s3.md
@@ -44,6 +44,17 @@ For `.netconfig`, just create or edit the file directly in the [desired location
For details on creating a credentials file go [here](https://docs.aws.amazon.com/sdk-for-net/v2/developer-guide/net-dg-config-creds.html#creds-file)
+#### Using SSO profiles
+
+If you are using an SSO profile, you must first log in using the AWS CLI before running sleet to allow SSO profiles to be used.
+
+Sleet will not prompt for SSO login.
+
+```
+aws sso login --profile my-sso-profile
+```
+
+
### Using accessKeyId and secretAccessKey in sleet.json
`sleet.json`:
diff --git a/src/SleetLib/FileSystem/FileSystemFactory.cs b/src/SleetLib/FileSystem/FileSystemFactory.cs
index 6242819..2fb3f5b 100644
--- a/src/SleetLib/FileSystem/FileSystemFactory.cs
+++ b/src/SleetLib/FileSystem/FileSystemFactory.cs
@@ -172,10 +172,19 @@ public static async Task CreateFileSystemAsync(LocalSettings s
if (!string.IsNullOrWhiteSpace(profileName))
{
var credFile = new SharedCredentialsFile();
+ var chain = new CredentialProfileStoreChain();
+
if (credFile.TryGetProfile(profileName, out var profile))
{
+ // Successfully created the credentials using the profile
amazonS3Client = new AmazonS3Client(profile.GetAWSCredentials(profileSource: null), config);
}
+ else if (chain.TryGetAWSCredentials(profileName, out var credentials))
+ {
+ // Successfully created the credentials using a profile with SSO
+ // This works for identities outside of AWS such as Azure AD and Okta
+ amazonS3Client = new AmazonS3Client(credentials, config);
+ }
else
{
throw new ArgumentException($"The specified AWS profileName {profileName} could not be found. The feed must specify a valid profileName for an AWS credentials file. For help on credential files see: https://docs.aws.amazon.com/sdk-for-net/v2/developer-guide/net-dg-config-creds.html#creds-file");
diff --git a/src/SleetLib/SleetLib.csproj b/src/SleetLib/SleetLib.csproj
index 496e036..3a43d0d 100644
--- a/src/SleetLib/SleetLib.csproj
+++ b/src/SleetLib/SleetLib.csproj
@@ -20,6 +20,8 @@
+
+
diff --git a/src/SleetLib/Utility/AmazonS3Utility.cs b/src/SleetLib/Utility/AmazonS3Utility.cs
index 4b24812..2d99f9e 100644
--- a/src/SleetLib/Utility/AmazonS3Utility.cs
+++ b/src/SleetLib/Utility/AmazonS3Utility.cs
@@ -1,5 +1,3 @@
-using System;
-
namespace Sleet
{
public static class AmazonS3Utility