create dedicated auth token pages for azure and snowflake#571
create dedicated auth token pages for azure and snowflake#571HarshCasper wants to merge 1 commit into
Conversation
HarshCasper
requested review from
quetzalliwrites and
remotesynth
as code owners
Deploying localstack-docs with
|
| Latest commit: |
6166fb0
|
| Status: | 🚫 Build failed. |
|
@bblommers @SimonWallner @mmaureenliu @lazarkanelov could you please review the |
|
what is the intent of this page? My understanding was that in the first phase we'll only have private access. This requires users to have a subscription that is then manually enabled for Azure. From a docs perspective there is nothing special around Azure. You use an auth token to access a subscription that gives you access to a product. During private preview, this access must be granted manually. |
Thanks Simon, I just want to make sure that the article reflects the current process, authentication token issuing, expiration time, etc. I'm not into this process, so I asked you guys to review the article. @SimonWallner @lazarkanelov @mmaureenliu @bblommers |
| To use the LocalStack for Azure emulator, a license with access to Azure is required. | ||
| You can get a license by registering on the [LocalStack Web Application](https://app.localstack.cloud/sign-up) and starting a trial, or by contacting the LocalStack team about an Azure-enabled plan. |
There was a problem hiding this comment.
The current behaviour is that everyone with a Pro subscription for AWS (either trial, base, team or enterprise) also has access to Azure.
So it is currently not necessary to contact support about an Azure-enabled plan.
What the right behaviour is, that I don't know - that's not my call 🙂
There was a problem hiding this comment.
Thanks @bblommers your description of the current behavior was exactly what we needed. We're currently discussing the licensing for public and private preview, and we'll update the article to reflect those changes. This will likely be a living document that we'll keep refining over the coming months. cc: @mmaureenliu @lazarkanelov
There was a problem hiding this comment.
Update: current process is described in https://www.notion.so/localstack/Azure-Private-Preview-26cfc2a234318055aaf3cf33acf0c1da?source=copy_link#35dfc2a234318060bc5ce1651def83b2
So basically what you've stated here is correct but I want to make it clearer:
- if you already have a LocalStack license (any license), contact support to add Azure access.
- if you don't have a LocalStack license, get a Hobby license (I'd rather they don't sign up for an AWS trial if they don't currently need one, and make use of that trial when they actually need to try AWS) then contact support to add Azure access
mmaureenliu
left a comment
mmaureenliu
left a comment
There was a problem hiding this comment.
Left comments based on current alignment on Azure private preview enrolment process. The Azure article needs fixing. I can't seem to find the snowflake article.
|
|
||
| - [LocalStack for Snowflake](/snowflake/getting-started/) | ||
| - [`localstack` CLI](/aws/getting-started/installation/#localstack-cli) | ||
| - A [LocalStack Auth Token](/snowflake/getting-started/auth-token/) |
There was a problem hiding this comment.
Am I really blind? But I didn't see this doc.
| An Auth Token is required to activate the LocalStack for Azure emulator. | ||
| It identifies and authenticates users outside the LocalStack Web Application, granting access to your workspace and to advanced features such as the Azure emulator image. | ||
|
|
||
| Auth Tokens are issued at the workspace level in [app.localstack.cloud](https://app.localstack.cloud) and are shared across every LocalStack product you use — the same token activates LocalStack for AWS, Azure, and Snowflake. |
There was a problem hiding this comment.
This is true for personal auth token but not CI auth token. CI auth token is tied to a subscription and would only work for the product within that subscription.
Caveat: for now, in multi-product scenario, snowflake and azure are just entitlements hitchhiking an aws subscription so both personal auth token and CI auth token would work in the same way. This will no longer be true once multi-product licensing support project is done.
I wonder if we could simply explain that personal auth token uniquely identifies a user in a workspace, and CI auth token uniquely identifies a subscription. And using an auth token will give you access to whatever product(s) that user or subscription has access to.
| To use the LocalStack for Azure emulator, a license with access to Azure is required. | ||
| You can get a license by registering on the [LocalStack Web Application](https://app.localstack.cloud/sign-up) and starting a trial, or by contacting the LocalStack team about an Azure-enabled plan. |
There was a problem hiding this comment.
Update: current process is described in https://www.notion.so/localstack/Azure-Private-Preview-26cfc2a234318055aaf3cf33acf0c1da?source=copy_link#35dfc2a234318060bc5ce1651def83b2
So basically what you've stated here is correct but I want to make it clearer:
- if you already have a LocalStack license (any license), contact support to add Azure access.
- if you don't have a LocalStack license, get a Hobby license (I'd rather they don't sign up for an AWS trial if they don't currently need one, and make use of that trial when they actually need to try AWS) then contact support to add Azure access
| To use the LocalStack for Azure emulator, a license with access to Azure is required. | ||
| You can get a license by registering on the [LocalStack Web Application](https://app.localstack.cloud/sign-up) and starting a trial, or by contacting the LocalStack team about an Azure-enabled plan. | ||
|
|
||
| After initiating your trial or acquiring a license, assign it to a user by following these steps: |
There was a problem hiding this comment.
After support confirms the license has access to the azure emulator
6 participants
Fixes DOC-156